On Sun, Mar 22, 2020 at 11:16:58AM +0000, Mark Rogers wrote:
On Sun, 22 Mar 2020 at 11:09, Chris Green cl@isbd.net wrote:
Something awry at 'the other end' maybe, I just tried:-
chris$ host debian.pool.ntp.org chris$Try: host 1.debian.pool.ntp.org
It looks like you need the subdomain.
Yes, but 'host debian.pool.ntp.org' shouldn't just return nothing should it?
I've tried several other sites where I know there is a.b.c.d and b.c.d and they all return IPs for both.
Interestingly see:-
chris$ host pool.ntp.org pool.ntp.org has address 51.140.97.99 pool.ntp.org has address 162.159.200.123 pool.ntp.org has address 109.74.206.120 pool.ntp.org has address 217.114.59.3 chris$ host debian.pool.ntp.org chris$ host 1.debian.pool.ntp.org 1.debian.pool.ntp.org has address 195.171.43.10 1.debian.pool.ntp.org has address 134.0.16.1 1.debian.pool.ntp.org has address 162.159.200.1 1.debian.pool.ntp.org has address 46.227.200.68 chris$
There are som intersting quirks in DNS now as IPv6 becomes more common, one thing it does often is cause a delay in one's first DNS lookup after not using it for a while. It can depend on what library call is being used to get the IP, some try both IPv4 and IPv6, some try only IPv4. Maybe the above oddity is another artefact of the same.
The response for debian.pool.ntp.org is definitely a bit wonky, I just tried nslookup too:-
chris$ nslookup debian.pool.ntp.org Server: 127.0.0.53 Address: 127.0.0.53#53
Non-authoritative answer: *** Can't find debian.pool.ntp.org: No answer
chris$ nslookup nurdle.isbd.uk Server: 127.0.0.53 Address: 127.0.0.53#53
** server can't find nurdle.isbd.uk: NXDOMAIN