# No IPv6 pool addresses?

**URL:** <https://community.ntppool.org/t/no-ipv6-pool-addresses/4794>\
**Category:** Client Configuration and Development\
**Tags:** dns, ipv6\
**Created:** [October 18, 2026, 8:10am UTC](https://community.ntppool.org/t/no-ipv6-pool-addresses/4794 "2026-10-18T08:10:35Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![MagicNTP](https://avatars.discourse-cdn.com/v4/letter/m/858c86/32.png) [@MagicNTP](https://community.ntppool.org/u/MagicNTP)\
**Post date:** [October 18, 2026, 8:01pm UTC](https://community.ntppool.org/t/no-ipv6-pool-addresses/4794/8 "2026-10-18T20:01:37Z")

</div>

We’ve been here before, and [that thread was closed](https://community.ntppool.org/t/the-time-has-come-we-must-enable-ipv6-entirely/1968/253) because the discussion had been going in circles. No point of continuing in circles here, with the same lack of outcome.

Regarding the question of more IPv6-enabled zones, @Ask wrote in that previous thread that he then was finishing cleaning up after the infrastructure move earlier this year, and working on the migration to PostgreSQL, and when that is done, IPv6 for more zones would be next.

The PostgreSQL update is available on the beta site, and when there’s no reports of issues in the coming weeks, it’ll get pushed to the production site, and likely will need some stabilization there. But then, once that is done, and while there’s no specific date yet, it seems to me that IPv6 enabled on more zones is starting to get within reach - without need to keep pushing, just a _bit_ more patience maybe (compared to the wait so far).

---

_[View the full topic](https://community.ntppool.org/t/no-ipv6-pool-addresses/4794)._
