Hi,
On Thu, Mar 27, 2025 at 09:38:02PM +1030, Mal wrote:
> Without the conf package, I still don't get why it populated only one
> ipv4 nameserver target and ignored the ipv6 target.
Are you sure this is not just what the installation process did?
Without "resolvconf" the /etc/resolv.conf file i
Hi,
On Thu, Mar 27, 2025 at 03:24:24PM -, Greg wrote:
> I wonder humorously if this discussion might devolve into yet another
> gargantuan thread concerning resolv.conf and whether it's kosher to set
> the immutable bit on that file in order to prevent whatever the heck is
> writing to it fro
On 2025-03-27, Andy Smith wrote:
> Hi,
>
> On Thu, Mar 27, 2025 at 09:11:23AM -0400, Greg Wooledge wrote:
>> On Thu, Mar 27, 2025 at 13:06:54 +, Andy Smith wrote:
>> > Without "resolvconf" the /etc/resolv.conf file is just a static file so
>> > there's limited things that would be editing it.
On Thu, Mar 27, 2025 at 13:58:49 +, Andy Smith wrote:
> I think all DHCP clients in Debian have a "Recomends" relationship on
> resolvconf to do this modification for them.
hobbit:~$ apt-cache show isc-dhcp-client | grep -e Recommends -e resolv
Recommends: isc-dhcp-common
Suggests: resolvconf,
Hi,
On Thu, Mar 27, 2025 at 09:11:23AM -0400, Greg Wooledge wrote:
> On Thu, Mar 27, 2025 at 13:06:54 +, Andy Smith wrote:
> > Without "resolvconf" the /etc/resolv.conf file is just a static file so
> > there's limited things that would be editing it. The guesses of "you"
> > or "the installer
On Thu, Mar 27, 2025 at 13:06:54 +, Andy Smith wrote:
> Hi,
>
> On Thu, Mar 27, 2025 at 09:38:02PM +1030, Mal wrote:
> > Without the conf package, I still don't get why it populated only one
> > ipv4 nameserver target and ignored the ipv6 target.
>
> Are you sure this is not just what the ins
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
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
> net
Hi,
On Thu, Mar 27, 2025 at 02:34:13PM +1030, Mal wrote:
> On Debian 6.1.129-1, I have a static network interface conf (no Netplan)
> with both IPv4 & IPv6 addressing and Name-servers set.
I don't know why only your IPv4 address is making it into resolv.conf,
but if the network setup is static th
The issue is the missing nameserver target in resolv. I am expecting
two in the echo.
Receiving records over the only nameserver target (v4) works fine
as expected - using DIG or ping.
In my configuration no IPv6 nameserver target is present in resolv,
hence it will never use IPv6 towards
Mal writes:
> On Debian 6.1.129-1, I have a static network interface conf (no Netplan)
> with both IPv4 & IPv6 addressing and Name-servers set.
[...]
> On another older machine (running kernel 4.9.35-v7+) with exactly the
> same configuration layout, I get BOTH the IPv4 & IPv6 addresses returne
Hello,
first of all the nameservers in /etc/resolv.conf are queried in order.
That means the 2'nd one is only queried when the first one does not
answer. Even NXDOMAIN is a valid answer.
So the first one should also return IPv6 over a IPv4 connection.
How do you query the nameserver? dig, 'get
12 matches
Mail list logo
