February 1997 - Test - lists.nanog.org

Re: h.root-servers.net broken
by James L. Fielding 14 Feb '97

14 Feb '97

All, The problem on h.root-servers.net is fixed. Temporarily lost the COM zone. Situation Normal: All Fixed Up. :-) Thanks for reporting the problem. If you have any more problems, please report them to our operations staff at (410)278-6829 or (410)278-6642. They'll contact me at home. James Fielding <jamesf(a)arl.mil>

3 2

Re: root servers more debug data
by Paul A Vixie 14 Feb '97

14 Feb '97

Btw, > Root nameserver F is not reachable from my network. I can't imagine why that would be so. Against my better judgement, I permit both traceroute and ping to this host.

1 0

Re: root server update
by DAVE NORDLUND 14 Feb '97

14 Feb '97

> Date: Thu, 13 Feb 1997 20:57:59 -0800 (PST) > From: matthew(a)scruz.net (Matthew Kaufman) > Subject: root server update > To: nanog(a)merit.edu > now, to add an infrequent check of the root nameservers to our homebrew NMS, > so our NOC operators can see these things happen as they happen, not after > the fact. So now everyone will start sending test DNS requests to the servers and overload them even further. > > -matthew kaufman > matthew(a)scruz.net > > Dave Nordlund d-nordlund(a)ukans.edu University of Kansas 913/864-0450 Computing Services FAX 913/864-0485 Lawrence, KS 66045 KANREN

4 3

Re: root server update
by queue＠echo.com 14 Feb '97

14 Feb '97

On Feb 14, 10:49, Randy Bush wrote: } Subject: Re: root server update } > So now everyone will start sending test DNS requests to the servers } > and overload them even further. } } What do you expect for folk who call people at home because they can't } figure out how to call a NOC? the appropriate NOC number isn't published anywhere i could find (and i looked- it's what i do). what did you do to try to fix or notify someone of this (rather major) problem? welcome to the new "it's not my problem, and i'm not logged in anyway" internet operators group. -Qarin Van Brink queue(a)scruz.net

2 1

did mci upgrade at mae-east?
by Craig Nordin 14 Feb '97

14 Feb '97

My little tester shows that we went from about 30% packet loss across MCI-MAE-East to maybe 1%. I saw some MCI "Outage" messages all pointing towards the 13th with downtime specified for rebuilding parts of the ATM section of the network. Maybe one of those repairs went in at MAE-East? Whatever it is, it looks better than it has since about September 20th when I started noticing severe packet-loss at MCI MAE-East. I hope it isn't just a fluke in my "sensors" :) Cheers! -- Craig Nordin -- cnordin(a)vni.net Virtual Networks http://www.vni.net

4 3

Re: root server update
by queue＠echo.com 14 Feb '97

14 Feb '97

hm. i count 10% of initial queries failing with a domain doesn't exist error, and that information then being cached so subsequent queries always fail, as being, as i said, a rather major problem. earthshaking, no; major, yes. many servers, in this instance, helps, but because the problem manifested itself as a root server not being *down*, but returning actually false information, the redundancy of the root servers meant that the odds were lower of failure, not that failure was avoided. a lot of mail was bouncing ("host unknown", on valid hosts), and a lot of queries were failing. am i "soooo important"? no. and i can flush my nameserver's cache to take care of a 1 in 10 problem looking up a site i'm trying to look up. but my users, and yours, are so important. and, happily, mr. fields, on his way to bed in maryland last night, wasn't so condescending. -Qarin Van Brink queue(a)scruz.net On Feb 14, 11:20, Randy Bush wrote: } Subject: Re: root server update } > what did you do to try to fix or notify someone of this (rather major) } > problem? } } major? funny, but i thought that was why we had many servers. } } and, not realizing it was a major earthshaking event, i sent email. silly } me. } } randy }-- End of excerpt from Randy Bush

1 0

root servers followup
by matthew＠scruz.net 14 Feb '97

14 Feb '97

This problem is definitely occuring on h.root-servers.net at the present time as documented below (similar to results that I see just arrived in my mailbox from <jh(a)yahoo.com>. However, an earlier log from our support department shows that d.root-servers.net and possibly e.root-servers.net were also having this problem within the past 60-90 minutes. (also see below) ; <<>> DiG 2.0 <<>> @g.root-servers.net mail.scruznet.com ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10 ;; flags: qr rd; Ques: 1, Ans: 0, Auth: 2, Addit: 2 ;; QUESTIONS: ;; mail.scruznet.com, type = A, class = IN ;; AUTHORITY RECORDS: SCRUZNET.com. 172800 NS NS.SCRUZ.NET. SCRUZNET.com. 172800 NS NS2.SCRUZ.NET. ;; ADDITIONAL RECORDS: NS.SCRUZ.NET. 172800 A 165.227.1.1 NS2.SCRUZ.NET. 172800 A 165.227.2.10 ;; Total query time: 433 msec ;; FROM: ns.scruz.net to SERVER: g.root-servers.net 192.112.36.4 ;; WHEN: Thu Feb 13 18:19:47 1997 ;; MSG SIZE sent: 35 rcvd: 123 ; <<>> DiG 2.0 <<>> @h.root-servers.net mail.scruznet.com ; (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: ;; mail.scruznet.com, type = A, class = IN ;; AUTHORITY RECORDS: . 86400 SOA A.ROOT-SERVERS.NET. hostmaster.INTERNIC.NET. ( 1997021100 ; serial 10800 ; refresh (3 hours) 900 ; retry (15 mins) 604800 ; expire (7 days) 86400 ) ; minimum (1 day) ;; Total query time: 157 msec ;; FROM: ns.scruz.net to SERVER: h.root-servers.net 128.63.2.53 ;; WHEN: Thu Feb 13 18:19:47 1997 ;; MSG SIZE sent: 35 rcvd: 108 -- earlier (sorry, nslookup, not dig) -- > server d.root-servers.net Default Server: d.root-servers.net Served by: - rs0.internic.net 198.41.0.5 ROOT-SERVERS.net - ns.ripe.net 193.0.0.193 ROOT-SERVERS.net - gw.home.vix.com 192.5.5.1 ROOT-SERVERS.net > cygnus.com Server: d.root-servers.net Served by: - rs0.internic.net 198.41.0.5 ROOT-SERVERS.net - ns.ripe.net 193.0.0.193 ROOT-SERVERS.net - gw.home.vix.com 192.5.5.1 ROOT-SERVERS.net Name: cygnus.com Served by: - C.ROOT-SERVERS.NET 192.33.4.12 com - D.ROOT-SERVERS.NET 128.8.10.90 com - E.ROOT-SERVERS.NET 192.203.230.10 com - I.ROOT-SERVERS.NET 192.36.148.17 com - F.ROOT-SERVERS.NET 192.5.5.241 com - G.ROOT-SERVERS.NET 192.112.36.4 com - A.ROOT-SERVERS.NET 198.41.0.4 com - H.ROOT-SERVERS.NET 128.63.2.53 com - B.ROOT-SERVERS.NET 128.9.0.107 com

3 2

phone equipment query
by William Allen Simpson 14 Feb '97

14 Feb '97

This is probably not the best place for this, but is vaguely an ISP operational issue: We are moving in a few weeks to a bigger building, and were going to change over from the usual separate wire lines to trunk-side T1s. The original Bell South quote was only $100 a month cheaper (including our own extra equipment costs amortized over 3 years), but every little bit helps. When we went to make the order today, Bell South suddenly changed its mind, forwarded us to a different person, and the new quote is _exactly_ the same per T1 as 24 separate lines, plus a much heftier installation charge ($5,100 versus earlier $2,750), plus our extra equipment costs. Phooey. Nothing doing. These costs are already twice as much as Ameritech (where I live, and which I always thought overpriced). So, we are looking very hard at the new FCC regs on unbundling. We will be very happy to offer combined telephone and internet service for the same rate (or less) than Bell South is charging for phone alone. The CO is only 2 blocks down the street. Our customer base is about 1/16 the residences, and 1/4 the Chamber of Commerce businesses in this small town, and we are adding 100 a month. But.... We are totally clueless in the phone vendor business. Anybody know where to find our own switching equipment? Any other hints? Heck, while I'm at it, where do I find out about ADSL equipment? WSimpson(a)UMich.edu Key fingerprint = 17 40 5E 67 15 6F 31 26 DD 0D B9 9B 6A 15 2C 32 BSimpson(a)MorningStar.com Key fingerprint = 2E 07 23 03 C5 62 70 D3 59 B1 4F 5E 1D C2 C1 A2

3 2

root servers
by matthew＠scruz.net 14 Feb '97

14 Feb '97

for the past few hours, we've been seeing certain root servers intermittently claiming that certain names don't exist, and then changing their mind a few minutes later. anyone else seeing this? did i miss an announcement of problems? -matthew kaufman matthew(a)scruz.net

4 3

whoops
by Brett L. Hawn 13 Feb '97

13 Feb '97

Apparently my posting was a wee bit premature, my 'source' hadn't set up the test domains yet. I would wait until morning to try them out as he's going to get them done tonight. [-] Brett L. Hawn (blh @ nol dot net) [-] [-] Networks On-Line - Houston, Texas [-] [-] 713-467-7100 [-]

1 0