[10479] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: genieweb.com answering for COM

daemon@ATHENA.MIT.EDU (Wheeler, Jesse W)
Thu Jul 3 14:16:21 1997

From: "Wheeler, Jesse W" <jesse_wheeler@reyrey.com>
To: "'nanog@merit.edu'" <nanog@merit.edu>
Date: Thu, 3 Jul 1997 10:51:44 -0700

Kinda makes you worried about the stability of the DNS system
if someone so small on the "food chain" can create such instablility.

------------------------------------------------------------------------
------------------------
Jesse W. Wheeler
QA/Systems Analyst

Reynolds & Reynolds
Healthcare Systems Division
Email: Jesse_Wheeler@reyrey.com 
------------------------------------------------------------------------
--------------------------------------------------------

>----------
>From: 	Rodney Joffe[SMTP:rjoffe@genuity.net]
>Sent: 	Thursday, July 03, 1997 10:46 AM
>To: 	'nanog@merit.edu'
>Subject: 	FW: genieweb.com answering for COM
>
><<File: ATT16935.ATT>>
>This has been corrected temporarily. With brute force ;-)
>
>Genieweb is a downstream customer of Los Nettos, one of our customers.
>No-one has been able to reach the company or the contact, so their T1
>was just taken down. I expect a call rather soon, so we can get them to
>fix their mistake.
>
>But it does bring up an interesting point.... is it that easy to create
>chaos? They are so far down the food chain, and yet....
>
>
>
>Rodney Joffe
>Chief Technology Officer
>Genuity Inc., a Bechtel company
>http://www.genuity.net
>
>
>
>> -----Original Message-----
>> From:	seanl@literati.org [SMTP:seanl@literati.org]
>> Sent:	Thursday, July 03, 1997 9:59 AM
>> To:	nanog@merit.edu
>> Subject:	genieweb.com answering for COM
>> 
>> com.    304     SOA     genieweb.com. root.genieweb.com. (
>>                         11      ; serial
>>                         10800   ; refresh (3 hours)
>>                         3600    ; retry (1 hour)
>>                         604800  ; expire (7 days)
>> 
>> This was cached on one our name servers.  Sure enough, dig any com
>> @genieweb.com shows:
>> 
>> ;; ANSWERS:
>> com.    86400   SOA     genieweb.com. root.genieweb.com. (
>>                         11      ; serial
>>                         10800   ; refresh (3 hours)
>>                         3600    ; retry (1 hour)
>>                         604800  ; expire (7 days)
>>                         86400 ) ; minimum (1 day)
>> com.    86400   NS      genieweb.com.
>>  
>> ;; AUTHORITY RECORDS:
>> com.    86400   NS      genieweb.com.
>>  
>> ;; ADDITIONAL RECORDS:
>> genieweb.com.   86400   A       198.147.97.23
>> 
>> I wonder if this is what has been causing random COM domain lookups to
>> fail for random people at random places.
>> 
>> The time I can see this affecting a name server is if it does a lookup
>> for a domain that's lamely delegated to genieweb.com, and then caches
>> the 'com' reply.
>> 
>> I've already left voicemail for the genieweb people.
>> 
>> 
>> -- 
>> Sean R. Lynch <seanl@literati.org> 
>
>

home help back first fref pref prev next nref lref last post