On Sun, Oct 11, 2015 at 07:37:24PM +0200, Pascal Hambourg wrote: > Dominic Hargreaves a écrit : > > On Sun, Oct 11, 2015 at 01:47:57PM +0200, Pascal Hambourg wrote: > >> > >> That may be generated from received IPv6 router advertisements (RA) by > >> rdnssd if installed. In that case, you can remove this package if you > >> don't need DNS resolution through the IPv6 server. Otherwise, check > >> whether the package resolvconf is installed. > > > > Aha! Thanks for the clue. > > > > The problem appears to have gone away after removing rdnssd, so I assume > > it was a particularly severe case of #740998 (an RC bug which was sadly > > not fixed in jessie). > > Even though I was aware of issues with rdnssd, I didn't know about this > RC bug. I'll check it. > > > I'll follow up on that bug (and probably a new bug against > > debian-installer to have rdnssd not installed). > > Problem is, rdnssd is required in an IPv6-only network with > autoconfiguration in order to fill /etc/resolv.conf, or a dual-stack > network with only autoconfigured IPv6 DNS. IME, installing resolvconf > solves the competition between the different DNS sources (RDNSS, DHCP > client, Network Manager...) for resolv.conf.
>From what I've read NM can do this and thus rdnssd is not required. It's certainly picking up the IPv6 resolver in my dual-stack network - it would be surprising if it behaved differently on a v6-only network. Dominic.
