564c3c3539
On Debian systems, unless configured by something else, there isn't an /etc/resolv.conf in the initramfs, which hinders DNS resolution. Tailscale has its fallback DNS functionality, but that has problems [1] in the corner-case situation of a Debian initramfs environment: - no /etc/resolv.conf means tailscale (or golang?) attempts to use 127.0.0.1 as a DNS resolver - the loopback interface (lo) isn't brought up in the initramfs. linux sends the DNS traffic off-device (destined for 127.0.0.1) Even with the Tailscale fix for that issue, it's a fallback and there's a noticeable delay, so do the correct thing here and create /etc/resolv.conf. [1] https://github.com/tailscale/tailscale/issues/6110
20 lines
627 B
Plaintext
20 lines
627 B
Plaintext
tailscale-initramfs (0.3) unstable; urgency=medium
|
|
|
|
* Configure resolv.conf in initramfs if it isn't already, so the tailscale
|
|
client can reach the control server more reliably.
|
|
|
|
-- Paul Aurich <paul@darkrain42.org> Wed, 03 May 2023 19:52:49 -0700
|
|
|
|
tailscale-initramfs (0.2) unstable; urgency=medium
|
|
|
|
* Keep trying to bring up the network until it either comes up or the boot
|
|
process continues.
|
|
|
|
-- Paul Aurich <paul@darkrain42.org> Tue, 06 Dec 2022 20:12:18 -0800
|
|
|
|
tailscale-initramfs (0.1) unstable; urgency=medium
|
|
|
|
* Initial Release.
|
|
|
|
-- Paul Aurich <paul@darkrain42.org> Fri, 14 Jan 2022 21:03:16 -0800
|