Craig A. Huegen
chuegen at quadrunner.com
Sat Aug 15 06:14:59 UTC 1998
This wouldn't be webteam.net, would it? =)
This morning, Chris Yarnell from NASA pointed out the response
to "dig @a.root-servers.net . soa":
. 2D IN NS PANIC.WEBTEAM.NET.
. 2D IN NS TORGO.WEBTEAM.NET.
PANIC.WEBTEAM.NET. 2D IN A 188.8.131.52
TORGO.WEBTEAM.NET. 2D IN A 184.108.40.206
I don't know how this happened, but it doesn't look pretty. =)
(The "standard" zone files were okay -- .COM, .NET, etc...)
On Fri, Aug 14, 1998 at 11:52:09PM -0500, max at inc.net wrote:
==> I am having some very bizzare DNS issues and am wondering if anyone
==> will be able to shed some light on this. A customer of ours started
==> recieving thousands of DNS requests for a wide range of domains,
==> mostly foreign. The requests are coming from a wide range of ips
==> most of which respond to nslookups "ie are nameservers". I have done
==> a whois on some of the domains and the 2 name servers having the
==> problems don't show up, I have also check to root servers and dont see
==> anything which would direct those domains to the name servers. Their
==> entire T1 is full from these requests about 1.2 meg. As the customer
==> is in the business of web hosting they can kill named nor can they
==> put up a packet filter to fix this. Also because there are literally
==> hundreds of diffrent domains both preforming the lookups and being
==> looked up it is not feasable to call the admin of each one to work
==> this out. Anyone have any ideas?
==>Internet Connect, INC.
==>max at inc.net
More information about the NANOG