ntp.org DNS lookups failing
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.
On Wed, Jan 18, 2017 at 02:15:32PM -0600, Douglas K. Rand via Outages <outages@outages.org> 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/8643239b33556257750a10a2cfd46600#gistcomm...
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 colangelod@wit.edu * wit.edu/dts * Follow us on Twitter @ DTSatWIT -----Original Message----- From: Outages [mailto:outages-bounces@outages.org] On Behalf Of Stephane Bortzmeyer via Outages Sent: Wednesday, January 18, 2017 3:20 PM To: Douglas K. Rand <rand@iteris.com> Cc: outages@outages.org Subject: Re: [outages] ntp.org DNS lookups failing On Wed, Jan 18, 2017 at 02:15:32PM -0600, Douglas K. Rand via Outages <outages@outages.org> 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/8643239b33556257750a10a2cfd46600#gistcomm... _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages
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, and the old servers failed / stopped to answer. One of our recursives lists these ;; ANSWER SECTION: ntp.org. 74239 IN NS ns2.everett.org. ntp.org. 74239 IN NS ns1.ntp.org. ntp.org. 74239 IN NS ns2.ntp.org. ntp.org. 74239 IN NS ns1.everett.org. ... and returns SERVFAIL to "pool.ntp.org" queries. The other one lists these: ;; ANSWER SECTION: ntp.org. 3509 IN NS anyns.pch.net. ntp.org. 3509 IN NS ns2.everett.org. ntp.org. 3509 IN NS ns3.p20.dynect.net. ntp.org. 3509 IN NS dns2.udel.edu. ntp.org. 3509 IN NS ns1.p20.dynect.net. ntp.org. 3509 IN NS ns2.p20.dynect.net. ntp.org. 3509 IN NS ns1.everett.org. ntp.org. 3509 IN NS dns1.udel.edu. ntp.org. 3509 IN NS ns4.p20.dynect.net. ... and happily answers queries.... Trying to query directly, ns1/ns2.ntp.org return SERVFAIL as well, and ns1/ns2.everett.org do not reply at all... so pure guesswork on my side says "the original set is broken / under attack / ..., so new servers have been added, but as long as the old NS records are still being cached, things keep failing". gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany gert@greenie.muc.de fax: +49-89-35655025 gert@net.informatik.tu-muenchen.de
On Wed, Jan 18, 2017 at 09:25:23PM +0100, Gert Doering via Outages <outages@outages.org> 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/8643239b33556257750a10a2cfd46600#gistcomm...
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 use.
participants (4)
-
Colangelo, Dom -
Douglas K. Rand -
Gert Doering -
Stephane Bortzmeyer