I am currently having this issue, but it might not be an ntp bug, but rather a kernel bug.
If you assign an IPv6 address to a virtual device composed of real sub-devices (e.g. to a bonding or bridge interface), the address will be wrongly detected as duplicate (marked as "tentative dadfailed"). See https://bugzilla.redhat.com/show_bug.cgi?id=503082 And this triggers the ntp messages because apparently ntp tries and fails to bind to the interface with the problematic address. My workaround to this issue was not assigning an IPv6 address to my bridge interface (I realized that it was not really needed in my case). ** Bug watch added: Red Hat Bugzilla #503082 https://bugzilla.redhat.com/show_bug.cgi?id=503082 ** Changed in: ntp (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/700492 Title: ntp complains about ipv6 errors every 5 minutes -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
