# Some geoDNS servers are not working
**URL:** https://community.ntppool.org/t/some-geodns-servers-are-not-working/3513
**Category:** GeoDNS Server
**Tags:** dns
**Created:** [September 15, 2024, 2:02pm UTC](https://community.ntppool.org/t/some-geodns-servers-are-not-working/3513 "2024-09-15T14:02:24Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@NTPman](https://community.ntppool.org/u/NTPman)
#### Post date: [September 15, 2024, 2:02pm UTC](https://community.ntppool.org/t/some-geodns-servers-are-not-working/3513/1 "2024-09-15T14:02:24Z")
Hello,
Some geoDNS servers are not working:
```auto
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:~ #
```
---
### Author:  [@ask](https://community.ntppool.org/u/ask)
#### Post date: [September 15, 2024, 7:53pm UTC](https://community.ntppool.org/t/some-geodns-servers-are-not-working/3513/2 "2024-09-15T19:53:02Z")
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).
---
### Author:  [@NTPman](https://community.ntppool.org/u/NTPman)
#### Post date: [September 16, 2024, 7:29am UTC](https://community.ntppool.org/t/some-geodns-servers-are-not-working/3513/3 "2024-09-16T07:29:54Z")
@ask, @gfk , thanks for taking care. There is another thing. Two geoDNS IP addresses are referred by multiple names:
```auto
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
```
---
### Author:  [@gfk](https://community.ntppool.org/u/gfk)
#### Post date: [September 19, 2024, 1:57am UTC](https://community.ntppool.org/t/some-geodns-servers-are-not-working/3513/4 "2024-09-19T01:57:04Z")
Thanks for headsup @NTPman ! The ipv6 servers should be fixed now. As for the dups, it looks like [g.ntpns.org](http://g.ntpns.org) is running stale data, I’ll see with @ask how to fix that!
---
### Author:  [@NTPman](https://community.ntppool.org/u/NTPman)
#### Post date: [January 4, 2025, 5:17pm UTC](https://community.ntppool.org/t/some-geodns-servers-are-not-working/3513/5 "2025-01-04T17:17:51Z")
It looks like there is different kind of problem (timeout instead of connection reset) with another server 2001:41d0:700:335d::8:
```auto
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.
---
### Author:  [@NTPman](https://community.ntppool.org/u/NTPman)
#### Post date: [January 20, 2025, 9:41am UTC](https://community.ntppool.org/t/some-geodns-servers-are-not-working/3513/6 "2025-01-20T09:41:08Z")
The geoDNS server with IP 160.119.216.201 joined the club of broken servers:
```auto
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.)
---
### Author:  [@NTPman](https://community.ntppool.org/u/NTPman)
#### Post date: [June 2, 2026, 7:36am UTC](https://community.ntppool.org/t/some-geodns-servers-are-not-working/3513/7 "2026-06-02T07:36:39Z")
Some update. Two geoDNS servers (2a0e:5c41:2:394:5054:ff:fe53:d711 [`a.ntpns.org`] and 2a0b:4342:1a91:d:216:3cff:fe94:b351 [`b.ntpns.org`]) are failing since a while:
```auto
dig +norecurse +tcp -t AAAA -q 2.pool.ntp.org @2a0e:5c41:2:394:5054:ff:fe53:d711
;; Connection to 2a0e:5c41:2:394:5054:ff:fe53:d711#53(2a0e:5c41:2:394:5054:ff:fe53:d711) for 2.pool.ntp.org failed: connection refused.
dig +norecurse +notcp -t AAAA -q 2.pool.ntp.org @2a0e:5c41:2:394:5054:ff:fe53:d711
; <<>> DiG 9.11.36-RedHat-9.11.36-13.el8 <<>> +norecurse +notcp -t AAAA -q 2.pool.ntp.org @2a0e:5c41:2:394:5054:ff:fe53:d711
;; global options: +cmd
;; connection timed out; no servers could be reached
dig +norecurse +tcp -t AAAA -q 2.pool.ntp.org @2a0b:4342:1a91:d:216:3cff:fe94:b351
;; Connection to 2a0b:4342:1a91:d:216:3cff:fe94:b351#53(2a0b:4342:1a91:d:216:3cff:fe94:b351) for 2.pool.ntp.org failed: connection refused.
dig +norecurse +notcp -t AAAA -q 2.pool.ntp.org @2a0b:4342:1a91:d:216:3cff:fe94:b351
; <<>> DiG 9.11.36-RedHat-9.11.36-13.el8 <<>> +norecurse +notcp -t AAAA -q 2.pool.ntp.org @2a0b:4342:1a91:d:216:3cff:fe94:b351
;; global options: +cmd
;; connection timed out; no servers could be reached
```
---
### Author:  [@MagicNTP](https://community.ntppool.org/u/MagicNTP)
#### Post date: [June 2, 2026, 9:13am UTC](https://community.ntppool.org/t/some-geodns-servers-are-not-working/3513/8 "2026-06-02T09:13:23Z")
Thanks for the hint, should be fixed now.
---
### Author:  [@NTPman](https://community.ntppool.org/u/NTPman)
#### Post date: [June 2, 2026, 12:08pm UTC](https://community.ntppool.org/t/some-geodns-servers-are-not-working/3513/9 "2026-06-02T12:08:59Z")
Much better now, thanks!