On 01/18/17 14:15, Douglas K. Rand via Outages wrote:
> All of our DNS queries in the ntp.org zone seem to be failing.
>
> Checked a few public DNS servers, such as Google's 8.8.8.8 and 8.8.4.4,
> and they are missing it also.
Back working again for us, and the public DNS servers that we often us
On Wed, Jan 18, 2017 at 09:25:23PM +0100,
Gert Doering via Outages wrote
a message of 52 lines which said:
> This looks like a name server set change, and the old servers failed /
> stopped to answer.
Right, and DNSDB supports this explanation:
https://gist.github.com/bortzmeyer/8643239b33
Hi,
On Wed, Jan 18, 2017 at 02:15:32PM -0600, Douglas K. Rand via Outages wrote:
> All of our DNS queries in the ntp.org zone seem to be failing.
>
> Checked a few public DNS servers, such as Google's 8.8.8.8 and 8.8.4.4,
> and they are missing it also.
This looks like a name server set change,
Can confirm similar behavior in Boston, MA as well
Dominick Colangelo * Systems Administrator * Technology Services * Wentworth
Institute of Technology * 550 Huntington Ave, Boston MA 02115 * 617-989-4523 *
email/im colange...@wit.edu * wit.edu/dts * Follow us on Twitter @ DTSatWIT
-Origina
On Wed, Jan 18, 2017 at 02:15:32PM -0600,
Douglas K. Rand via Outages wrote
a message of 10 lines which said:
> All of our DNS queries in the ntp.org zone seem to be failing.
Works for me but, indeed, fails from several places.
Investigation in progress:
https://gist.github.com/bortzmeyer/8
All of our DNS queries in the ntp.org zone seem to be failing.
Checked a few public DNS servers, such as Google's 8.8.8.8 and 8.8.4.4,
and they are missing it also.
This is from North Dakota.
___
Outages mailing list
Outages@outages.org
https://puck.net
service was restored about 08:30 GMT today (20170118), having dropped
at 19:30 GMT yesterday (20170117) according to our external
monitoring.
I note that the VPS we have there wasn't rebooted, it looks like it
was just a network issue rather than someome temporarily pulling the
plug on the e
