# Problems with Cloudflare DNS in NZ **URL:** \ **Category:** Server operators\ **Created:** [September 15, 2024, 5:13am UTC](https://community.ntppool.org/t/problems-with-cloudflare-dns-in-nz/3512 "2024-09-15T05:13:18Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![gombadi](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/gombadi/32/1486_2.png) [@gombadi](https://community.ntppool.org/u/gombadi)\ **Post date:** [September 15, 2024, 5:13am UTC](https://community.ntppool.org/t/problems-with-cloudflare-dns-in-nz/3512/1 "2024-09-15T05:13:18Z")
Hi All I am seeing issues with the DNS records being returned by Cloudflare public dns system (1.1.1.1) for `pool.ntp.org`. Not for other domains like `2.nz.pool.ntp.org` but only the global name. I am guessing this is NOT a problem with the pool DNS system but was wanting to get an idea if others around the world were seeing similar issues or the problem was isolated to NZ. If, from an ip address in New Zealand, I do a `AAAA` lookup for `2.pool.ntp.org` I **always** , and **only** get the two Cloudflare ntp ip addresses. ```auto $ dig +short AAAA @1.1.1.1 2.pool.ntp.org 2606:4700:f1::123 2606:4700:f1::1 ``` If I do an `AAAA` dig to `i.ntpns.org` I get these two plus a selection of other servers as expected. For ipv4 `A` requests I am seeing the Cloudflare ipv4 addresses along with a number of ip addresses returned that are in Argentina. These addresses are in the pool and if they are yours and you are seeing extra requests coming through then they may be coming from across the Pacific - [pool.ntp.org: Statistics for 168.96.251.195](https://www.ntppool.org/scores/168.96.251.195) for example. Anyway as I mentioned I do NOT think this is a problem with the pool dns systems but was wanting to ask others if they have, or are seeing similar things from their location before I contact Cloudflare, if they have some support portal for their public DNS system. And for the record there are no problems with `8.8.8.8`, `9.9.9.9` or my local ISP DNS and the responses from Cloudflare are coming from a location that is about 20ms from me which puts them in Auckland New Zealand - the Cloudflare POP location. Thanks. ---
**Author:** ![Bas](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/bas/32/465_2.png) [@Bas](https://community.ntppool.org/u/Bas)\ **Post date:** [September 15, 2024, 3:03pm UTC](https://community.ntppool.org/t/problems-with-cloudflare-dns-in-nz/3512/2 "2024-09-15T15:03:24Z")
I get more… nslookup [2.nz.pool.ntp.org](http://2.nz.pool.ntp.org) 1.1.1.1 Server: 1.1.1.1 Address: 1.1.1.1#53 Non-authoritative answer: Name: [2.nz.pool.ntp.org](http://2.nz.pool.ntp.org) Address: 103.242.70.5 Name: [2.nz.pool.ntp.org](http://2.nz.pool.ntp.org) Address: 103.242.70.4 Name: [2.nz.pool.ntp.org](http://2.nz.pool.ntp.org) Address: 202.21.136.135 Name: [2.nz.pool.ntp.org](http://2.nz.pool.ntp.org) Address: 103.158.134.33 Name: [2.nz.pool.ntp.org](http://2.nz.pool.ntp.org) Address: 2406:e001:f:61::1 Name: [2.nz.pool.ntp.org](http://2.nz.pool.ntp.org) Address: 2407:f100:0:1::3 Name: [2.nz.pool.ntp.org](http://2.nz.pool.ntp.org) Address: 2606:4700:f1::1 Name: [2.nz.pool.ntp.org](http://2.nz.pool.ntp.org) Address: 2407:f100:0:1::2 There are 2 comming from: telesmart.co.nz But you shouldn’t use local pools anymore, as the number of severs could be too low and/or get overloaded. The delay doesn’t matter that much, it will be compensated in the client. I fail to see the problem. ---
**Author:** ![NTPman](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ntpman/32/450_2.png) [@NTPman](https://community.ntppool.org/u/NTPman)\ **Post date:** [September 15, 2024, 3:44pm UTC](https://community.ntppool.org/t/problems-with-cloudflare-dns-in-nz/3512/4 "2024-09-15T15:44:20Z")
From Switzerland this is what I get: ```auto # dig +short AAAA @1.1.1.1 2.pool.ntp.org 2a00:7580:60:211::46 2001:4168:3::2 2001:8a8:4008::109 2001:918:cafe::123 ``` (The first IP is one of the server I am maintaining) From France this is what I get: ```auto # dig +short AAAA @1.1.1.1 2.pool.ntp.org 2001:41d0:2:c837::123 2001:bc8:255e:200::1 2606:4700:f1::1 2001:bc8:255e:100::1 ``` I do not encounter the problem you are seeing. ---
**Author:** ![bjh21](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/bjh21/32/1181_2.png) [@bjh21](https://community.ntppool.org/u/bjh21)\ **Post date:** [September 16, 2024, 11:03am UTC](https://community.ntppool.org/t/problems-with-cloudflare-dns-in-nz/3512/5 "2024-09-16T11:03:34Z")
I notice that Argentina only has two IPv6 servers in the NTP Pool, and they’re both Cloudflare ones. So the observed behaviour is what you’d expect if you were getting the correct servers for Argentina rather than for New Zealand. (And to confirm, 1.1.1.1 is returning perfectly sensible results for me in the UK) ---
**Author:** ![gombadi](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/gombadi/32/1486_2.png) [@gombadi](https://community.ntppool.org/u/gombadi)\ **Post date:** [September 17, 2024, 7:51pm UTC](https://community.ntppool.org/t/problems-with-cloudflare-dns-in-nz/3512/6 "2024-09-17T19:51:49Z")
Thanks @bjh21 and @NTPman Your replies were helpful. I guess the problem is with the NZ Cloudflare POP so will contact them to see what can be done. I am not aware of anything that checks and validates the DNS replies from providers like Cloudflare. If anyone is then let me know. May have a look at building a tool that checks what the DNS providers are sending out is actually similar to what the pool DNS servers are providing.