I called our DNS vendor and he said he was getting 100 calls per hour.
said something was up with the internic servers.
How many of you in dns land had strange things happen today ???
a.root-servers.net, which is run by NSI and is THE authority for many of the
tld's. The NSI database spit out bad data for the tld zone files, and human
error allowed the bad data to be loaded on a.root-servers.net. Servers b-i
subsequently loaded the bad data from a. Only the com and net zones were
affected, and only a handful of the root's were affected (for any leangth
of time, anyway).
See below for the 'official' explanation from NSI (as seen on nanog).
Michael
Date: Thu, 17 Jul 1997 22:52:18 +0500 (GMT)
From: David Holtzman <dho...@internic.net>
To: na...@merit.edu
Subject: NSI bulletin 097-004 | Root Server Problems
Resent-Date: Thu, 17 Jul 1997 14:42:42 -0400 (EDT)
On Wednesday night, July 16, during the computer-generation of the
Internet top-level domain zone files, an Ingres database failure resulted
in corrupt .COM and .NET zone files. Despite alarms raised by Network
Solutions' quality assurance schemes, at approximately 2:30 a.m. (Eastern
Time), a system administrator released the zone file without regenerating the
file and verifying its integrity. Network Solutions corrected the
problem and reissued the zone file by 6:30 a.m. (Eastern Time).
Thank you.
David H. Holtzman
Sr VP Engineering, Network Solutions
dho...@internic.net
Art Upton (aau...@nfor.com) wrote:
: we saw a dns brownout this morning that show all