July 1997 - Test - lists.nanog.org

genieweb.com answering for COM
by seanl＠literati.org 03 Jul '97

03 Jul '97

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(a)literati.org>

3 2

Re: URGENT! Root Servers not updated
by Marc Slemko 03 Jul '97

03 Jul '97

On Thu, 3 Jul 1997, John Hawkinson wrote: > > Erm... most routing databases use asxxxx, but the NIC uses xxxx. eg. > > whois -h whois.internic.net 6171 > > Doesn't anybody read the instructions around here? MY GOODNESS! > > whois nnnn > > will return all records that match "nnnn", be they people, domains, > AS numbers, networks, or what-have-you. No need to get snarky. You can do it the way you suggest to get only ASes. Or you can skip that to get a list of all records and, in the rare case that there is more than one, do another lookup on that one. On Thu, 3 Jul 1997, Christian Nielsen wrote: > On Wed, 2 Jul 1997, Marc Slemko wrote: > > > Note, however, that just because an AS shows as not existing in the > > InterNIC's database doesn't mean it doesn't exist. From what the InterNIC > > has told me, they have no policy of having pointer records for AS blocks > > allocated to regional registries; it happens sometimes, it doesn't happen > > sometimes, all depending on what they feel like doing. That means that to > > find the owner of an AS you may need to query every regional registery in > > the world. Right now there are few enough such registries to make it > > possible, but it is certainly an annoyance. > > But if you were to go to > > ftp://rs.internic.net/netinfo/asn.txt > > You can see who they belong to. Really? As I said, they do it if they feel like and don't if they don't meaning that some they do. Some, such as the one that as8221 is out of, they don't. For the ones that they do, there are pointers in the whois database saying "oh, go look there" just like there are for netblocks. > PS. I also know that the above file is out of date and needs to be When I asked the InterNIC about it, the response I got for the above block was not that it had not yet been updated, but that it just hadn't been done, no reason for it.

5 4

Re: FW: genieweb.com answering for COM
by Joseph C. Pistritto 03 Jul '97

03 Jul '97

At 10:32 AM 7/3/97 -0700, Rodney Joffe wrote: Yeah it is. Wait till someone steals your network numbers by broadcasting them and their ISP isn't filtering. It's Happened Before. This is one of the things we don't want the press writing about. How darned easy it is for some person making a silly mistake to introduce a big transient problem until it gets killed. Fortunately, people pay attention and kill these things off reasonably quickly, but it makes managing the net a much more "active" thing than one would think at first inspection. A lot of management at a lot of companies (even ISPs), doesn't realize this. The problem of course is that we can't scale the number of people who know how to fix things like this nearly as fast as we can (and are) scaling the network. The whole thing needs to be a lot more insensitive to minor screwups. The fact that most of our protocols (like especially DNS and even to an extent BGP) were designed when the universe of people who would be managing them was much smaller. The problem gets worse when people use old protocols (like DNS) that were intended for one thing (nameing) to implement something different (like load balancing) "because it works". Kind of. On the other hand, with the installed base, replacing old protocols is getting really difficult. As an industry, we need to move this process forward. The network grows while you sleep... -jcp- PS: Personal note: This is my last week at PointCast, hence the 'jcphome' address. That's my permanent address. -jcp- >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(a)literati.org [SMTP:seanl@literati.org] >> Sent: Thursday, July 03, 1997 9:59 AM >> To: nanog(a)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(a)literati.org> > >Attachment Converted: "D:\PCNMAIL\ATT16935.ATT" >

1 0

Re: Keynote/Boardwatch Internet Backbone Index A better test!!!
by randy＠psg.com 03 Jul '97

03 Jul '97

I rerecommended the study Ben Black first recommended because it was ingeniously end to end. And real end to end, not end to web. randy

1 0

Re: Root Servers not updated
by Sean Donelan 03 Jul '97

03 Jul '97

>Lastly, it appears irresponsible to fan the flames of "the internic is >trying to get over" via lists like these. How about giving us the benefit >of the doubt? We generally stay silent on these issues, but feel that it >is important to explain what we are doing and why. No, we are not trying >to take over the net. Sorry for the confusion. I'm sorry, I must have missed a message somewhere. On which list did NSI post the announcement about the corrupt zone files preventing the other root servers from updating or the announcement about the changes for those FTPing the zone files prior to Mr. Vixie's message? -- Sean Donelan, Data Research Associates, Inc, St. Louis, MO Affiliation given for identification not representation

2 1

Root Servers not updated
by David H. Holtzman 03 Jul '97

03 Jul '97

There's a lot of smoke going around this list and others about the root servers. The internic generated a corrupt zone file on Tuesday which Bind did not load and prevented XFERs to the secondaries. We became aware of it last night and it is currently fixed. New zones will be ready for XFER within the next hour. The issue with requiring a login for retrieving the zone files was designed to help reduce spamming. We are currently experiencing a huge system load due to several individuals who are trying to register recently deleted domain names. The requests are being repeated and fired off every few milliseconds. One individual has over 50,000 templates in the system as we speak. We believe that by requiring an identity to download the zone files we will better protect the community. Note that this ftp policy has not yet gone into effect. Lastly, it appears irresponsible to fan the flames of "the internic is trying to get over" via lists like these. How about giving us the benefit of the doubt? We generally stay silent on these issues, but feel that it is important to explain what we are doing and why. No, we are not trying to take over the net. Sorry for the confusion. David H. Holtzman Senior VP Engineering, NSI dholtz(a)internic.net

3 2

FW: genieweb.com answering for COM
by Rodney Joffe 03 Jul '97

03 Jul '97

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(a)literati.org [SMTP:seanl@literati.org] > Sent: Thursday, July 03, 1997 9:59 AM > To: nanog(a)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(a)literati.org>

2 1

RE: genieweb.com answering for COM
by Wheeler, Jesse W 03 Jul '97

03 Jul '97

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(a)reyrey.com ------------------------------------------------------------------------ -------------------------------------------------------- >---------- >From: Rodney Joffe[SMTP:rjoffe@genuity.net] >Sent: Thursday, July 03, 1997 10:46 AM >To: 'nanog(a)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(a)literati.org [SMTP:seanl@literati.org] >> Sent: Thursday, July 03, 1997 9:59 AM >> To: nanog(a)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(a)literati.org> > >

1 0

Re: URGENT! Root Servers not updated
by Carl Oppedahl 03 Jul '97

03 Jul '97

At 12:31 PM 07/03/97 -0400, Gordon Cook wrote: >has the basic problem that paul vixie complained about been solved? > >I called a knowledgable source last night. That person was aware of the >change and said that the proper IANA people had been informed in advance >and had (he thought) not disagreed. the change he believed was not for any >of the reasons that paul feared. So there is some *good* reason why the root level servers of the Internet should be out of synch with each other, slightly over half of them carrying data that is out of date by almost a week? Did your source happen to address this issue?

1 0

Re: URGENT! Root Servers not updated
by David Stoddard 03 Jul '97

03 Jul '97

Hank Nussbacher writes: > On a related note, how do people these days determine who is the owner of > an AS# that is registered with Internic? All attempts for the past 2 > months with commands like "whois -h whois.internic.net asxxxx" result in > totally corrupted data. Leave off the "as" in the front of the number and it should work just fine. If you prefix it with "as" it thinks you are looking for a NIC handle. Dave Stoddard US Net Incorporated 301-572-5926 dgs(a)us.net

2 1