|
The interfaces.d directory was empty. > root@debian:/home/user:/etc/network/interfaces.d# ls -lt total 0 Adding that package did add the missing v6 nameserver successfully - thank you Greg ! To your question on the resolv.conf file - on another 12.10 machine, I have the same conf and the file was not being updated on restart. > root@debian2:/home/user# ls -lt resol* -rw-r--r-- 1 root root 24 Mar 21 15:40 resolv.conf root@debian2:/home/user# uptime 21:31:03 up 1 day, 6:20, 2 users, load average: 0.00, 0.00, 0.00 Without the conf package, I still don't get why it populated only one ipv4 nameserver target and ignored the ipv6 target. On 27/03/2025 9:18 pm, Greg Wooledge
wrote:
On Thu, Mar 27, 2025 at 14:34:13 +1030, Mal wrote:root@debian:/home/user# more /etc/network/interfaces source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback allow-hotplug enp1s0 iface enp1s0 inet static address 12.34.56.78 network 12.34.56.0 netmask 255.255.255.0 broadcast 12.34.56.255 gateway 12.34.56.1 iface enp1s0 inet6 static address 2xxx:xxxx:x00:1::50 netmask 64 gateway 2xxx:xxxx:x00:1::1 dns-nameservers 12.34.56.80 2xxx:xxx:x00:1::80That dns-nameservers line is only used if you're running the "resolvconf" package.When I query what is set in resolv.conf file, It only returns the IPv4 host. root@debian:/home/user# more /etc/resolv.conf nameserver 12.34.56.80I would look at the timestamp on that file. Is it being updated at all? Next, I would verify that you've installed the resolvconf package, since your configuration is relying on it. Or, as another person suggested already, skip the resolvconf package entirely, and just use a static resolv.conf file. |