% check-soa -i pool.ntp.org
a.ntpns.org.
2620:101:d007::42: OK: 1484769062 (3 ms)
207.171.17.42: OK: 1484769062 (2 ms)
b.ntpns.org.
2001:8e0:ffff:1::282: OK: 1484769062 (15 ms)
212.25.19.23: OK: 1484769062 (17 ms)
193.243.171.138: OK: 1484769062 (30 ms)
174.127.124.192: OK: 1484769062 (100 ms)
c.ntpns.org.
85.214.25.217: OK: 1484769062 (22 ms)
2a01:238:426b:900:4535:f84f:5043:4854: OK: 1484769062 (24 ms)
2a00:14b0:4200:32e0::1e5: OK: 1484769062 (31 ms)
89.36.18.22: OK: 1484769062 (48 ms)
d.ntpns.org.
2a01:4f8:121:43cd::3:1: OK: 1484769062 (14 ms)
178.63.120.205: OK: 1484769062 (15 ms)
199.188.48.59: OK: 1484769062 (100 ms)
199.249.223.53: OK: 1484769062 (210 ms)
e.ntpns.org.
94.242.223.210: OK: 1484769062 (0 ms)
2001:4b20:0:ca01:5054:ff:fe6f:c4fb: OK: 1484769062 (16 ms)
46.234.32.107: OK: 1484769062 (15 ms)
173.255.139.202: OK: 1484769062 (141 ms)
f.ntpns.org.
2a02:2290:2:48::73: OK: 1484769062 (2 ms)
46.29.176.73: OK: 1484769062 (2 ms)
31.3.105.98: OK: 1484769062 (13 ms)
2001:4b20:0:ca01:5054:ff:fe69:9149: OK: 1484769062 (15 ms)
46.234.32.105: OK: 1484769062 (15 ms)
2a03:7900:104:1::2: OK: 1484769062 (22 ms)
g.ntpns.org.
37.123.115.71: OK: 1484769062 (9 ms)
h.ntpns.org.
2a01:238:426b:900:4535:f84f:5043:4854: OK: 1484769062 (21 ms)
45.127.112.23: OK: 1484769062 (53 ms)
i.ntpns.org.
2a02:2290:2:48::73: OK: 1484769062 (9 ms)
45.127.113.23: OK: 1484769062 (10 ms)
-
-
Save bortzmeyer/8643239b33556257750a10a2cfd46600 to your computer and use it in GitHub Desktop.
Ours was botched for a few hours too. Flushed the ntp.org. entry to refresh the NS set and we're back now.
Used the Flush Cache function on the GPD site to flush NS records for ntp.org and pool.ntp.org.
My local Google instance is responding correctly after that:
sadiq@lasciel:~/dev/ > dig pool.ntp.org @8.8.8.8
; <<>> DiG 9.10.3-P4-Ubuntu <<>> pool.ntp.org @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 57924
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;pool.ntp.org. IN A
;; ANSWER SECTION:
pool.ntp.org. 137 IN A 206.108.0.132
pool.ntp.org. 137 IN A 192.95.25.79
pool.ntp.org. 137 IN A 167.114.204.238
pool.ntp.org. 137 IN A 199.19.167.36
;; Query time: 26 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Jan 18 20:52:14 UTC 2017
;; MSG SIZE rcvd: 105
Or with my local Unbound
That's a mighty impressive response time. Any input on how I can make it that good? I resolve to root DNS zones, not ISP DNS/public DNS.
@bortzmeyer Three of the four old servers have been down for months; I've been nagging the folks in charge of the ntp.org domain to get it updated and we recently got the in-zone NS-set updated to include PCH and Dyn. The delegation was updated today, but as you saw it looks like the one working server of the old four had a hiccup. :-(
The passive DNS service DNSDB supports Gert Doering's explanation: