After my previous note about (as it turned out) www.pool.ntp.org having
gone unrouted, I got one more automated notification before it got
fixed. Since then it's been fine - until now. I just got another
failure, timestamped "Wed, 10 Nov 2010 20:25:21 -0500 (EST)". The
syndrome looks the same as before, both the symptom ("No route to host"
in my cronjob's output) and the investigation (traceroute6 working
until it hits the default free zone and showing !N then).
Apparently the fix didn't stay fixed? I suppose this one could be a
one-off failure, but it seems unlikely - when it went out before, it
was the first time I'd ever seen such failures; one-off routing
failures were not exactly common. So I don't expect that's what's
wrong here either.
But, since I appear to be effectively the only person who actually
notices this (it went for three days, before, and apparently nobody
else noticed until I mentioned it), I thought I should get the word out
promptly this time. :)
/~\ 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
