November 1998 - Test - lists.nanog.org

NANOG 14 thanks
by David Diaz 12 Nov '98

12 Nov '98

I wanted to thank everyone who came and helped with NANOG 14. It was an absolute pleasure to meet everyone who attended. If there is a regret it's that we wish there was time to met with everyone there. Our engineers were universally excited and greatful to have the opportunity to exchange experiences with all those they spoke with. It was an honor as well as a pleasure to host nanog. I highly recommend it to anyone even considering it. It may look like work but it was all Fun. Thanks again to all especially the Merit folks. Next time no oversubscription factor on the power strips. 1 strip per attendee a must!! David PS-Anyone needing power strips or anything else for another NANOG I think we may be able to help. And next time PLEASE dont flood ping Bellsouth, they have no sense of humor! Thank you, David Diaz Chief Technical Officer Netrail, Inc email: davediaz(a)netrail.net pager: 888-576-1018 office: 888-NETRAIL Fax: 404 522-2191 Colo facilities: Atlanta-NAP, Miami, Arlington, Chicago, San Francisco ------------------------------------------------- Hosting NANOG 14 in Atlanta Nov 8-10

1 0

was i asleep when the gtld servers had the worse problem today?
by Paul A Vixie 11 Nov '98

11 Nov '98

http://www.news.com/News/Item/0,4,28664,00.html?st.ne.fd.mdh

4 3

Re: QUICKER FIX Re: [fjk].gtld-servers.net bogus for .com
by Scott Gifford 11 Nov '98

11 Nov '98

>> > Many thanks to my friend & cow-orker Tristan Horn for this >> > idea...in BIND 8 you can define servers as bogus (meaning >> > "don't ever trust these") as follows: >> > >> > // [fjkl].root-servers.net >> > server 192.5.5.241 { bogus yes; }; >> > server 198.41.0.10 { bogus yes; }; >> > server 193.0.14.129 { bogus yes; }; >> > server 198.32.64.12 { bogus yes; }; > >i recommend against that. > Do you recommend against this particular way of telling BIND to temporarily ignore name servers which are known to be a little, errr, funky? Or do you recommend against ignoring broken name servers in general?.. I guess what I really would like to know is how did you handle this problem? :) Just wondering, --------Scott.

2 1

WCCP talk..
by alex＠nac.net 11 Nov '98

11 Nov '98

Unfortunately, stage fright prevents me from asking this question on the NANOG meeting floor. My understanding of WCCP is that the server is responsible to tell the WCCP-enabled Cisco router that, "Hey, I'm alive to recieve port 80 requests!" My question is, what prevents a cache from seding a WCCP frame saying, "Hey, I'm alive" when it really isn't? Is there a way for the router to check the cache in the opposite direction? Seems odd that your would rely on the cache to verify that the cache is OK. -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Atheism is a non-prophet organization. I route, therefore I am. Alex Rubenstein, alex(a)nac.net, KC2BUO, ISP/C Charter Member Father of the Network and Head Bottle-Washer Net Access Corporation, 9 Mt. Pleasant Tpk., Denville, NJ 07834 Don't choose a spineless ISP; we have more backbone! http://www.nac.net -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

6 14

ANS routing problems?
by Aleksi.Suhonen＠saunalahti.fi 11 Nov '98

11 Nov '98

Hello, We are having routing problems with ANS. They are not accepting our routes from AS3561. They were excepting them just fine about a week ago, but around last week end our routes dissappeared from their AS. Current status, with AT&T as an example of a working routing status: route-views.oregon-ix.net>sh ip b r ^1673_.+_6667 route-views.oregon-ix.net>sh ip b r ^7018_.+_6667 BGP table version is 4987768, local router ID is 198.32.162.100 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path * 195.74.0.0/19 12.127.0.249 0 7018 3561 5556 6667 i * 195.197.0.0/16 12.127.0.249 0 7018 3561 5556 6667 i * 195.218.64.0/19 12.127.0.249 0 7018 3561 5556 6667 i * 195.238.192.0/19 12.127.0.249 0 7018 3561 5556 6667 i Since all their NS and MX records are within their own network, contacting them is rather impossible, so I turn to the NANO group for helpful hints on how to resolve the problem. -- Aleksi Suhonen Network Development Saunalahden Serveri Oy AXU-RIPE

2 1

[fjk].gtld-servers.net bogus for .com
by Marc Slemko 11 Nov '98

11 Nov '98

[fjk].gtld-servers.net (which are listed as authoritative for .com) are giving bogus authoritative nxdomain results for all the .com domains I tried. eg. ; <<>> DiG 2.2 <<>> internic.com @f.gtld-servers.net ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 10 ;; flags: qr aa rd; Ques: 1, Ans: 0, Auth: 1, Addit: 0 ;; QUESTIONS: ;; internic.com, type = A, class = IN ;; AUTHORITY RECORDS: COM. 86400 SOA A.ROOT-SERVERS.NET. hostmaster.INTERNIC.NET. ( 1998111000 ; serial 1800 ; refresh (30 mins) 900 ; retry (15 mins) 604800 ; expire (7 days) 86400 ) ; minimum (1 day) ;; Total query time: 67 msec ;; FROM: valis.worldgate.com to SERVER: f.gtld-servers.net 207.159.77.18 ;; WHEN: Wed Nov 11 11:17:16 1998 ;; MSG SIZE sent: 30 rcvd: 107 f.root-servers.net is giving non-authoritative "sorry, I don't do that, here are the nameservers for .com" responses. I have sent mail to the InterNIC, but just in case you were wondering why you are seeing what you may be seeing. Symptoms of this problem are being told by your resolver that various domains do not exist once in a while.

9 11

Re: [fjk].gtld-servers.net bogus for .com
by Dean Robb 11 Nov '98

11 Nov '98

At 15:36 11/11/98 -0600, you wrote: > >Fixed on the next daily update? So when the AOL problem happened, a special >update was done, but when several hundred (anyone know how many really) >entries are trashed, we all must wait until the next daily update? Another Public Relations/Customer Service triumph for NSI/InterNIC. </sarcasm> I suspect more than just the fjk servers are hosed...last night around midnight I was surfing and had over ten sites disappear between one load and the next. The domain names ran the gamut from "f" to "u". Given the time frames, they likely disappeared as the update propagated. Now, either a whole lot of sites simultaneously had server crashes or.... Spammers should be investigated by Ken Starr! Dean Robb PC-EASY computer services (757) 495-EASY [3279]

1 0

Re: QUICKER FIX Re: [fjk].gtld-servers.net bogus for .com
by Paul Vixie 11 Nov '98

11 Nov '98

> f.root-servers.net is FTP'ing its COM zone even as we speak. AXFR to > a.root-servers.net is giving wierd results. i'll be fetching the zone > manually until we find the smoking gun. btw, i've taken F offline while the FTP happens. though the response f.root-servers.net was sending back (an upward delegation) was just a "lame server" and would not have caused errors, whereas the error that f.gtld-servers.net was sending this morning would have caused false negatives (bounced mail, etc). -- Paul Vixie <paul(a)vix.com>

1 0

Re: QUICKER FIX Re: [fjk].gtld-servers.net bogus for .com
by Paul Vixie 11 Nov '98

11 Nov '98

> > Many thanks to my friend & cow-orker Tristan Horn for this > > idea...in BIND 8 you can define servers as bogus (meaning > > "don't ever trust these") as follows: > > > > // [fjkl].root-servers.net > > server 192.5.5.241 { bogus yes; }; > > server 198.41.0.10 { bogus yes; }; > > server 193.0.14.129 { bogus yes; }; > > server 198.32.64.12 { bogus yes; }; i recommend against that. > Note that f.gtld-servers.net was the long-running one giving real > problems. [fjk].gtld-servers.net were the ones I saw giving false > nxdomains at ~1000 pdt, [jk] were fixed by ~1030 and f was taken down > ~1200. Two hours! Sheesh. indeed. > It appears to be fixed now. f.gtld-servers.net is down, a few others are > giving referals to the .com nameservers (still "broken", but doesn't break > things the same). right. > By fixed, I mean you shouldn't see false nxdomains and things should all > resolve fine. f.root-servers.net is FTP'ing its COM zone even as we speak. AXFR to a.root-servers.net is giving wierd results. i'll be fetching the zone manually until we find the smoking gun. -- Paul Vixie <paul(a)vix.com>

1 0

NameServer Monitoring System
by joe＠vpop.net 11 Nov '98

11 Nov '98

Howdy folks, I am looking for BETA testers for our "NameServer Monitoring System". (no this does not check the roots to see if they are operational ;-) ) Basically, it watches the roots for changes to the nameservers you monitor and emails you those changes on a daily basis. A sample output is at: http://www.domainwatch.com/monitor/example.html You can monitor up to 10 nameservers. Anyways, if you're interested, do the form bit at: http://www.domainwatch.com/monitor/ and we'll get the instructions out to you. Send bug reports, flames and kudos to admin(a)domainwatch.com Thanks, -joe -- NewsHub: http://www.NewsHub.com/tech/ | DomainSurfer: http://www.DomainSurfer.com/ | Explore Your Net! MultiTrace: http://www.MultiTrace.com/ |

1 0