# It's 2019 and still no IPv6 by default?

**URL:** <https://community.ntppool.org/t/its-2019-and-still-no-ipv6-by-default/972>\
**Category:** Uncategorized\
**Tags:** dns\
**Created:** [November 5, 2018, 10:58pm UTC](https://community.ntppool.org/t/its-2019-and-still-no-ipv6-by-default/972 "2018-11-05T22:58:31Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![imcdona](https://sea2.discourse-cdn.com/flex016/user_avatar/community.ntppool.org/imcdona/32/253_2.png) [@imcdona](https://community.ntppool.org/u/imcdona)\
**Post date:** [October 10, 2019, 4:50pm UTC](https://community.ntppool.org/t/its-2019-and-still-no-ipv6-by-default/972/16 "2019-10-10T16:50:09Z")

</div>

I noticed that on the CentOS 8 installs I’ve done they’re using a **single pool statement** rather than multiple server lines in `/etc/chrony.conf`

What’s interesting is that they’re using the IPv6 capable pool address [2.centos.pool.ntp.org](http://2.centos.pool.ntp.org) instead of say 0.centos or 1.centos.

I wonder if IPv6 had anything to do with their decision to use 2.centos?

**The chrony config in previous versions of CentOS looked like this:**

```
server 0.centos.pool.ntp.org iburst
server 1.centos.pool.ntp.org iburst
server 2.centos.pool.ntp.org iburst
server 3.centos.pool.ntp.org iburst

```

Correct me if I’m wrong but when using the _ **server** _ option instead of the _ **pool** _ option that config would only ever resolve 1 IPv6 NTP source.

**The chrony config in CentOS 8 looks like this:**

`pool 2.centos.pool.ntp.org iburst`

The new config using the pool option with `2.centos.pool.ntp.org` has the potential to resolve multiple IPv6 NTP sources as opposed to a single source.

I wonder if we’ll see an increase in IPv6 NTP traffic?

In case you’re wondering, CentOS 8 was released on September 24th 2019.

---

_[View the full topic](https://community.ntppool.org/t/its-2019-and-still-no-ipv6-by-default/972)._