Some geoDNS servers are not working

GeoDNS Server
1

Hello,

Some geoDNS servers are not working:

tumbleweed:~ # dig pool.ntp.org @2a0b:4341:1500:142:5054:ff:fef5:ba1c
;; communications error to 2a0b:4341:1500:142:5054:ff:fef5:ba1c#53: connection refused
;; communications error to 2a0b:4341:1500:142:5054:ff:fef5:ba1c#53: connection refused
;; communications error to 2a0b:4341:1500:142:5054:ff:fef5:ba1c#53: connection refused

; <<>> DiG 9.18.25 <<>> pool.ntp.org @2a0b:4341:1500:142:5054:ff:fef5:ba1c
;; global options: +cmd
;; no servers could be reached

tumbleweed:~ # dig pool.ntp.org @2a05:91c0:1506:145::
;; communications error to 2a05:91c0:1506:145::#53: connection refused
;; communications error to 2a05:91c0:1506:145::#53: connection refused
;; communications error to 2a05:91c0:1506:145::#53: connection refused

; <<>> DiG 9.18.25 <<>> pool.ntp.org @2a05:91c0:1506:145::
;; global options: +cmd
;; no servers could be reached

tumbleweed:~ # dig pool.ntp.org @2600:3c02::f03c:92ff:fe5f:baf1
;; communications error to 2600:3c02::f03c:92ff:fe5f:baf1#53: connection refused
;; communications error to 2600:3c02::f03c:92ff:fe5f:baf1#53: connection refused
;; communications error to 2600:3c02::f03c:92ff:fe5f:baf1#53: connection refused

; <<>> DiG 9.18.25 <<>> pool.ntp.org @2600:3c02::f03c:92ff:fe5f:baf1
;; global options: +cmd
;; no servers could be reached

tumbleweed:~ #
2

Thanks @NTPman – the monitoring systems we use are somewhat oblivious to IPv6 (thankfully DNS generally is, too, or at least is resilient to this).

We can hopefully fix and if not then disable the IPv6 delegation to those servers (cc @gfk).

2 Likes
3

@ask, @gfk , thanks for taking care. There is another thing. Two geoDNS IP addresses are referred by multiple names:

c.ntpns.org has address 212.12.50.229
g.ntpns.org has address 212.12.50.229
d.ntpns.org has address 46.101.53.6
g.ntpns.org has address 46.101.53.6
1 Like
4

Thanks for headsup @NTPman ! The ipv6 servers should be fixed now. As for the dups, it looks like g.ntpns.org is running stale data, I’ll see with @ask how to fix that!

2 Likes
5

It looks like there is different kind of problem (timeout instead of connection reset) with another server 2001:41d0:700:335d::8:

tumbleweed:~ # dig pool.ntp.org @2001:41d0:700:335d::8
;; communications error to 2001:41d0:700:335d::8#53: timed out
;; communications error to 2001:41d0:700:335d::8#53: timed out
;; communications error to 2001:41d0:700:335d::8#53: timed out

; <<>> DiG 9.20.2 <<>> pool.ntp.org @2001:41d0:700:335d::8
;; global options: +cmd
;; no servers could be reached
tumbleweed:~ #

The server 2001:43f8:d60:300::201 has different kind of problem (routing?); it is mostly unreachable from North America. It is OK from the rest of the world, so it rather looks like routing issue.

1 Like
6

The geoDNS server with IP 160.119.216.201 joined the club of broken servers:

dig +tcp -t AAAA -q 2.pool.ntp.org @160.119.216.201
;; Connection to 160.119.216.201#53(160.119.216.201) for 2.pool.ntp.org failed: connection refused.

(There is still quiet high redundancy, only three servers are broken.)

1 Like