A kind of "minimum working set" is available as ipv6 atm:
ntp.ubuntu.com
2.ubuntu.pool.ntp.org
And obviously also (ipv6.ntp.ubuntu.com)
The good thing is that this should get everything working:
- ntp will find an ipv6 at least on 2....
- and ntpdate defaulting to ntp.ubuntu.com should work as well
With that the original request (ipv6 to ntp.ubunut.com) is solved, yet
fix released isn't really applying as it was no package update. Since I
have only tested that marginally on a LXD test system that can't reach a
lot of targets I'd encourage the reporter (and more if willing) to
retest this if things are now working properly for you? Therefore
setting incomplete to let anybody finding an issue remaining reopen it
if needed.
Also the question at Canonical Sysadmins: Any plans/progress on enabling
the other[013].ubuntu.pool.ntp.org as well?
** Changed in: ntp (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ntp in Ubuntu.
https://bugs.launchpad.net/bugs/715141
Title:
Default NTP servers do not have AAAA records
Status in ntp package in Ubuntu:
Incomplete
Bug description:
Binary package hint: ntp
When installing ntp on an IPv6 only host, the kindly provided ntp.ubuntu.com
does not work, because it does not have a AAAA record.
Please provide IPv6 connectivity for this host.
This affects all releases.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/715141/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
