Re: ntpd ignoring resolv.conf

On Tue, Sep 24, 2024 at 08:16:16AM GMT, Maks wrote:

> Sep 24 07:38:38 ufr-t14 ntpd[33259]: error resolving pool 0.de.pool.ntp.org:
> Name does not resolve (8)
> Sep 24 07:38:39 ufr-t14 ntpd[33259]: error resolving pool 1.de.pool.ntp.org:
> Name does not resolve (8)
> Sep 24 07:38:40 ufr-t14 ntpd[33259]: error resolving pool
> 0.freebsd.pool.ntp.org: Name does not resolve (8)
> Sep 24 07:38:41 ufr-t14 ntpd[33259]: error resolving pool
> 2.freebsd.pool.ntp.org: Name does not resolve (8)

> For some strange reason ntpd ignores resolv.conf and expects a DNS
> server on the loopback interface.

I had similar messages as long as I ignored ipv6, i.e. when my
external interface had no global v6 address and there was no v6 entry
in resolv.conf.  Now that I have taken the time to configure that, it
seems to have fixed itself.  I'm not saying I'm sure your problem is
the same, but just in case try to fully configure ipv6.

Maybe nptd wants to use v6 really badly and when no other v6
nameserver is available it tries ::1. Which would be a bug :-P

-- 
Ian