# The time has come: we must enable IPv6 entirely **URL:** \ **Category:** Pool Development\ **Created:** [April 13, 2021, 7:56pm UTC](https://community.ntppool.org/t/the-time-has-come-we-must-enable-ipv6-entirely/1968 "2021-04-13T19:56:59Z")\ **Posts on this page:** 1\ **Showing post:** 253
**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:** [April 30, 2026, 6:29pm UTC](https://community.ntppool.org/t/the-time-has-come-we-must-enable-ipv6-entirely/1968/253 "2026-04-30T18:29:31Z")
At day-job most deployments everywhere are IPv6 only, for all the obvious reasons. It works fine. Many many deployments are IPv6-only now. Nothing is being taken away from correctly configured legacy IPv4-only deployments by enabling this. I’m going to close this thread; you are all just going in circles. We will have AAAA records on the standard pool names. I’m sorry it’s taken so many years. It keeps being like the third big item on the hobby-work todo list. The main holdup is human bandwidth to track and deal with any problems it might cause. I trust that some of you who have been strong advocates for this change sooner rather than later will be able and willing to help when the time comes. I need to stabilize things after the recent cluster move, then finish the migration to postgres and then it’s again the next thing on the list. --- _[View the full topic](https://community.ntppool.org/t/the-time-has-come-we-must-enable-ipv6-entirely/1968)._