# Marco will be happy....more IPv6 servers

**URL:** <https://community.ntppool.org/t/marco-will-be-happy-more-ipv6-servers/2356>\
**Category:** Uncategorized\
**Created:** [April 24, 2022, 9:26pm UTC](https://community.ntppool.org/t/marco-will-be-happy-more-ipv6-servers/2356 "2022-04-24T21:26:27Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**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:** [April 24, 2022, 9:26pm UTC](https://community.ntppool.org/t/marco-will-be-happy-more-ipv6-servers/2356/1 "2022-04-24T21:26:27Z")

</div>

@ [marco.davids](https://community.ntppool.org/u/marco.davids)

You will be happy.

I made my 2 VPS-servers also use IPv6.

So my own pool ntp.heppen.be contain 4 servers where 2 are dual stack:

[https://manage.ntppool.org/manage/servers?a=19sfa9p](https://manage.ntppool.org/manage/servers?a=19sfa9p)

```auto
bas@workstation:~$ nslookup ntp.heppen.be
Server: 127.0.0.53
Address:	127.0.0.53#53

Non-authoritative answer:
Name:	ntp.heppen.be
Address: 5.196.189.119
Name:	ntp.heppen.be
Address: 77.109.90.72
Name:	ntp.heppen.be
Address: 89.207.129.63
Name:	ntp.heppen.be
Address: 82.168.89.20
Name:	ntp.heppen.be
Address: 2001:41d0:a:4558::9752:705b
Name:	ntp.heppen.be
Address: 2a00:7b80:477:21::9dcb:d174

```

I forgot all about them having with IP6 DNS-records.

Hope you like it.

---

<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:** [April 25, 2022, 12:14pm UTC](https://community.ntppool.org/t/marco-will-be-happy-more-ipv6-servers/2356/2 "2022-04-25T12:14:47Z")

</div>

> [@Bas](#):
>
> Hope you like it.

I do!

It would be even better though if @ask would add AAAA-records to all instances of the pool and not just the 2.pool-instance.

---

<div class="post-metadata">

**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:** [April 25, 2022, 4:23pm UTC](https://community.ntppool.org/t/marco-will-be-happy-more-ipv6-servers/2356/3 "2022-04-25T16:23:47Z")

</div>

I agree.

I do not understand he gives just 4 NTP’s and not 6 or 8, like 4x IPv4 and 2x IPv6 on all.  
Systems that run in prio IPv6 will pick the IPv6 servers and if not there the IPv4’s.

I doubt he must change much code.

Just offer more pool servers 😄

I should not matter for the load on them as Chrony (do not know about NTP) lowers the requests on other then the best server anyway by polling them less.

Minpoll / Maxpoll works good for that.

---

<div class="post-metadata">

**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:** [May 1, 2022, 6:38pm UTC](https://community.ntppool.org/t/marco-will-be-happy-more-ipv6-servers/2356/4 "2022-05-01T18:38:39Z")

</div>

Finally, the latest Beta of the Fritzbox does let me do IPv6 properly with a firewall and a no nonsense approach.

I have added another server to the IPv6 pool.

ntp.heppen.be now servers 4xIPv4 and 3xIPv6 😃

---

<div class="post-metadata">

**Author:** ![rishabhlakhotia](https://avatars.discourse-cdn.com/v4/letter/r/839c29/32.png) [@rishabhlakhotia](https://community.ntppool.org/u/rishabhlakhotia)\
**Post date:** [May 6, 2022, 6:28am UTC](https://community.ntppool.org/t/marco-will-be-happy-more-ipv6-servers/2356/5 "2022-05-06T06:28:18Z")

</div>

Adding to this, I am running three NTP servers and all of them are IPv6 enabled. Funny though, only two of them have IPv4 addresses.

I’m pro IPv6 and we need more zones to be v6 enabled. I’ll add one more server with IPv6 in India zone by next month.

---

<div class="post-metadata">

**Author:** ![eric8bits](https://avatars.discourse-cdn.com/v4/letter/e/df788c/32.png) [@eric8bits](https://community.ntppool.org/u/eric8bits)\
**Post date:** [May 6, 2022, 7:08am UTC](https://community.ntppool.org/t/marco-will-be-happy-more-ipv6-servers/2356/6 "2022-05-06T07:08:43Z")

</div>

Mine has IPv6 as well including AAAA record and reverse. IPv6 FTW!

---

<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:** [May 9, 2022, 8:43am UTC](https://community.ntppool.org/t/marco-will-be-happy-more-ipv6-servers/2356/7 "2022-05-09T08:43:48Z")

</div>

Great to hear, but the real problem (or should I say, the remaining problem right now) is the missing AAAA-records in \*.pool.ntp.org.

[0.pool.ntp.org](http://0.pool.ntp.org) does not have one  
[1.pool.ntp.org](http://1.pool.ntp.org) does not have one  
[3.pool.ntp.org](http://3.pool.ntp.org) does not have one

Only [2.pool.ntp.org](http://2.pool.ntp.org) (and the variants, like [2.vendor.pool.ntp.org](http://2.vendor.pool.ntp.org) and [2.country.pool.ntp.org](http://2.country.pool.ntp.org)) have an AAAA.

That’s sad and I wish it would be fixed. ☹
