My monitoring-monitoring cronjob has been telling me > nc: connect www.pool.ntp.org [2607:f238:2::51/80]: No route to host
for a while now (specifically, since the run whose mail was timestamped "Thu, 4 Nov 2010 02:25:21 -0400 (EDT)"). It's not an operational issue - it retries over v4 just fine - but it seems to me like an indication of some kind of problem. It's not as simple as my v6 connectivity going out; I can reach 2001:4f8:3:7:230:48ff:fec6:9aaa (ftp.netbsd.org's v6 address) just fine. traceroute6 to www.pool.nt.org tells me traceroute to ntppool-varnish.develooper.com (2607:f238:2::51), 30 hops max, 12 byte packets 1 Stone 2.197 ms 2.149 ms * 2 2610:98:8001:1::2 20.206 ms 20.056 ms 21.12 ms 3 2610:98:1::1 19.715 ms 23.343 ms 20.268 ms 4 2001:470:0:41::1 105.317 ms !N 107.428 ms !N 104.822 ms !N It's not at all clear to me what's wrong here; superficially, looks like a routing snafu, but after three days I would ahve expected a routing hiccup to have fixed itself. Is there anything I can do to help get it, whatever it is, fixed? /~\ The ASCII Mouse \ / Ribbon Campaign X Against HTML [email protected] / \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
