----- Original Message -----
From: "esr" <esr@thyrsus.com> To: "Majdi S. Abbas" <msa@latt.net> Cc: "jra" <jra@baylink.com>, "North American Network Operators' Group" <nanog@nanog.org> Sent: Monday, April 3, 2017 10:34:21 PM Subject: Re: NTP problems/time.windows.com?
Majdi S. Abbas <msa@latt.net>:
Haven't seen it, but if people are reporting sudden hour offsets, on the first Monday in April, I'd bet on a DST implementation bug that hijacked the system clock on their servers.
This doesn't look like the sort of error you'd get with a free running clock.
I concur, about the one-hour shift anyway. The random garbage times aren't really likely either - jumps that large would tend to get the source rejected as a falseticker.
It's a weird set of symptoms that rather looks as if they hit two different failure modes at once. Dunno.
It's not entirely clear whether it's *entirely* MSWin clients; I can't imagine anything being pointed at those servers that wasn't, though, cause who the hell would? Anyone smart enough to manually select NTP upstreams isn't going *there*... Cheers, -- jra -- Jay R. Ashworth Baylink jra@baylink.com Designer The Things I Think RFC 2100 Ashworth & Associates http://www.bcp38.info 2000 Land Rover DII St Petersburg FL USA BCP38: Ask For It By Name! +1 727 647 1274