# Intention to enable IPv6 by default in 2017

**URL:** <https://community.ntppool.org/t/intention-to-enable-ipv6-by-default-in-2017/91>\
**Category:** Announcements\
**Created:** [January 4, 2017, 5:52am UTC](https://community.ntppool.org/t/intention-to-enable-ipv6-by-default-in-2017/91 "2017-01-04T05:52:58Z")\
**Posts on this page:** 1\
**Showing post:** 99

<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:** [August 3, 2025, 10:42pm UTC](https://community.ntppool.org/t/intention-to-enable-ipv6-by-default-in-2017/91/99 "2025-08-03T22:42:43Z")

</div>

The coverage of IPv6 monitoring is A LOT more sparse than IPv4 monitors. With the new monitoring system it’s much easier to run dual-stack monitors (just one daemon and setup process).

Link to instructions in [the monitor operator](https://community.ntppool.org/t/ntp-pool-agent-v4-0-2/3998) section.

---

_[View the full topic](https://community.ntppool.org/t/intention-to-enable-ipv6-by-default-in-2017/91)._