We notice this here as well, as we're increasingly turning up new services and VMs without IPv4. It fails with a rather cryptic error message:
Jul 8 07:10:03 rpki-validator ntpdate[689]: Can't find host ntp.ubuntu.com: Name or service not known (-2)
Jul 8 07:10:03 rpki-validator ntpdate[689]: no servers can be used, exiting
Jul 8 07:10:03 rpki-validator ntpdate[726]: Can't find host ntp.ubuntu.com: Name or service not known (-2)
Jul 8 07:10:03 rpki-validator ntpdate[726]: no servers can be used, exiting
If the Ubuntu sysadmin team does not manage to dual-stack their public NTP service in three years, perhaps it is time for the ntpdate package to switch to 2.pool.ntp.org?
We notice this here as well, as we're increasingly turning up new services and VMs without IPv4. It fails with a rather cryptic error message:
Jul 8 07:10:03 rpki-validator ntpdate[689]: Can't find host ntp.ubuntu.com: Name or service not known (-2)
Jul 8 07:10:03 rpki-validator ntpdate[689]: no servers can be used, exiting
Jul 8 07:10:03 rpki-validator ntpdate[726]: Can't find host ntp.ubuntu.com: Name or service not known (-2)
Jul 8 07:10:03 rpki-validator ntpdate[726]: no servers can be used, exiting
If the Ubuntu sysadmin team does not manage to dual-stack their public NTP service in three years, perhaps it is time for the ntpdate package to switch to 2.pool.ntp.org?
Tore