# Odd NS setting for \`g.ntpns.org\`

**URL:** <https://community.ntppool.org/t/odd-ns-setting-for-g-ntpns-org/2038>\
**Category:** Server operators\
**Tags:** dns\
**Created:** [June 30, 2021, 9:10am UTC](https://community.ntppool.org/t/odd-ns-setting-for-g-ntpns-org/2038 "2021-06-30T09:10:19Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![giovane](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/giovane/32/755_2.png) [@giovane](https://community.ntppool.org/u/giovane)\
**Post date:** [June 30, 2021, 9:10am UTC](https://community.ntppool.org/t/odd-ns-setting-for-g-ntpns-org/2038/1 "2021-06-30T09:10:19Z")

</div>

So `[a--i].ntpns.org` are the authoritative servers for `pool.ntp.org` (`dig ns pool.ntp.org`)

Each server of `[a--i].ntpns.org` has no NS record associated with it, which is OK.  
Except for `g.ntpns.org`.

To illustrate that for `a.ntpns.org`:

```auto
$dig ns a.ntpns.org

;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25602
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;a.ntpns.org. IN NS

;; AUTHORITY SECTION:
ntpns.org. 3600 IN SOA ns1.us.bitnames.com. dnsoper.bitnames.com. 2020070800 7200 3600 3628800 3600
;; Query time: 97 msec

```

For `g.ntpns.org`, in turn:

```auto
dig ns g.ntpns.org  

; <<>> DiG 9.11.5-P4-5.1+deb10u5-Debian <<>> ns g.ntpns.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30653
;; flags: qr rd ra; QUERY: 1, ANSWER: 7, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;g.ntpns.org. IN NS

;; ANSWER SECTION:
g.ntpns.org. 43200 IN NS d.ntpns.org.
g.ntpns.org. 43200 IN NS i.ntpns.org.
g.ntpns.org. 43200 IN NS h.ntpns.org.
g.ntpns.org. 43200 IN NS a.ntpns.org.
g.ntpns.org. 43200 IN NS c.ntpns.org.
g.ntpns.org. 43200 IN NS f.ntpns.org.
g.ntpns.org. 43200 IN NS e.ntpns.org.

```

This is not per se a configuration error, it is simply an inconsistency. Maybe it is intentional, just want to see if folks are aware of this

---

<div class="post-metadata">

**Author:** ![ask](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/ask/32/907_2.png) [@ask](https://community.ntppool.org/u/ask)\
**Post date:** [July 3, 2021, 12:13pm UTC](https://community.ntppool.org/t/odd-ns-setting-for-g-ntpns-org/2038/2 "2021-07-03T12:13:16Z")

</div>

yeah, it’s intentional. A handful of the [dns servers](https://www.ntppool.org/dns-server.html) are particularly regional, so they’re “behind” the [g.ntpns.org](http://g.ntpns.org) name which will return a different IP when queried from some regions.

---

<div class="post-metadata">

**Author:** ![marco.davids](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/marco.davids/32/767_2.png) [@marco.davids](https://community.ntppool.org/u/marco.davids)\
**Post date:** [July 14, 2021, 10:34am UTC](https://community.ntppool.org/t/odd-ns-setting-for-g-ntpns-org/2038/3 "2021-07-14T10:34:15Z")

</div>

I wish I understood this, but I don’t 🤔