--
You received this message because you are subscribed to the Google Groups "public-ntp-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to public-ntp-disc...@googlegroups.com.
To post to this group, send email to public-nt...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/public-ntp-discuss/93e6033b-7a67-4af0-9010-c30e47c07be0%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Greetings.We monitor the IPv6 and IPv4 addresses. We have not observed any failures but I'll admit that our IPv6 monitoring could be improved. I'm not aware of any issues that would be affecting IPv6 and not IPv4, I'll do a bit of research.Can you send us a bit more information:- What are affected IP addresses?- Can you provide a traceroute from your device to the affected IPs?- Are you using native IPv6, 6to4, or any other tunneling?- Does this happen at a particular time of day?
On Tue, Oct 16, 2018 at 11:11 AM <eit...@bittech.co.il> wrote:
Hello,--I have just configured few dozens of network devices to use time.google.com and time2.google.com and 3 and 4 as their NTP servers.The NTP logs from all the devices shows that every few queries the IPv6 address, of various Google NTP servers, not anyone specific - are not reachable.No such issue at all with the IPv4 addresses of all Google's NTP servers.Does Google monitor these IPv6 addresses? verifies their reliability?
You received this message because you are subscribed to the Google Groups "public-ntp-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to public-ntp-discuss+unsub...@googlegroups.com.