You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Sam Rasins <Sa...@Caribe-Enterprises.com> on 1997/07/18 06:45:33 UTC
More info on the recent problems on the 'Net
-------INFO-----
07-17-97
Laurence Kahn, the guy that ported BIND to NT, discovered the a.root
problem last nite. An individual on his mailing list noticed that he was
having some problems with TLD's, not all, just some. There was no name
resolution. IP's worked fine, just no DNS -- again not on all TLD's. He
had problems thru about 7:30am this morning. He talked to some ISP
type's that were flushing their DNS cache today to make sure no erroneous
info was still hanging around.
Also heard MAE-West was down yesterday due to a power outage and was still
not fully functional as of noon today. Haven't heard any more about that.
--------FORWARDED MESSAGE------
From: David Holtzman <dh...@internic.net>
Subject: NSI bulletin 097-004 | Root Server Problems
To: nanog@merit.edu
Date: Thu, 17 Jul 1997 22:52:18 +0500 (GMT)
MIME-Version: 1.0
Sender: owner-nanog@merit.edu
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
dholtz@internic.net