- NANOG - lists.nanog.org

gTLD Informational Message
by Brad Verd 17 Feb '01

17 Feb '01

This is an Informational Message to the internet community: Tuesday, the 20th, Verisign Global Registry Services will be removing a.root-servers.net from the authoritative NS set serving com/net/org. In it's place we will be adding l.gtld-servers.net to the authoritative NS set. The new set of servers authoritative for these TLDs will be: A.GTLD-SERVERS.NET. 6D IN A 198.41.3.38 E.GTLD-SERVERS.NET. 6D IN A 207.200.81.69 F.GTLD-SERVERS.NET. 6D IN A 198.17.208.67 J.GTLD-SERVERS.NET. 6D IN A 210.132.100.101 K.GTLD-SERVERS.NET. 6D IN A 213.177.194.5 M.GTLD-SERVERS.NET. 6D IN A 202.153.114.101 G.GTLD-SERVERS.NET. 6D IN A 198.41.3.101 C.GTLD-SERVERS.NET. 6D IN A 205.188.185.18 I.GTLD-SERVERS.NET. 6D IN A 192.36.144.133 B.GTLD-SERVERS.NET. 6D IN A 203.181.106.5 D.GTLD-SERVERS.NET. 6D IN A 208.206.240.5 L.GTLD-SERVERS.NET. 6D IN A 192.41.162.30 This will not require any change to root.cache file and a.root-servers.net will provide answers for com, net, and org in parallel for enough time to accommodate the zones TTL's. -------------------------------------- Brad Verd Operations Manager Resolution Systems Verisign Global Registry Services Email - bverd(a)verisign.com ---------------------------------------

1 0

Upgrade season
by Sean Donelan 17 Feb '01

17 Feb '01

It seems like a lot of folks have run into software upgrade problems all together. @Home, Telocity, Abovenet, Exodus and probably more recently had some type of snafu which their customer service people said was related to upgrades in progress. Are we at that point in the upgrade cycle where everyone needs to make changes at the same time? It doesn't seem to be a common vendor problem, as far as I can tell it was a different issue in each case. But after a relatively slow period in December (holidays) and January; I noticed an uptick in people sending me mail about issues during the first couple of weeks of February. I'm theorizing there is some natural calendar function which results in people doing upgrades about the same time at the beginning of February. The same thing seemed to happen with California power plants. After being down only 3,000MW; in February California is down 10,000MW of plant capacity due to scheduled and unscheduled maintenance.

3 2

NANOG meeting and the XFL
by Mike Gibbs 17 Feb '01

17 Feb '01

If anyone wants to go, several of us are driving to Birmingham AL to what the XFL game on Sunday. The game is at 3pm cst and Birmingham is 157 miles from Atlanta. Tickets are still available. Mike Gibbs

1 0

Lan connectivity loss
by Kevin_Badeen＠harte-hanks.com 16 Feb '01

16 Feb '01

Scenario, We have a meshed network, with two primary hub sites, Router A and Router B. {Internet} | [Inet-rtr] | [core-rtr]-------------------<[router a]--------------------< frame cloud | ||||||||||||| [Router C]--------------<[Router B]--------------------<frame cloud Router A lost it's connection to the frame cloud. All of the sites hanging off of Router B (via PVC's) began to experience the same problem: The routers were able to ping internet addresses, but the workstations on the local LAN's were not. However, the workstations were able to ping Router B's serial interfaces facing the cloud, but could not get through to Router C. All routers in organization are running eigrp, as well as using static routes. All routers are in the same AS. Router B 's local LAN was able to ping any internet address. When Router A's frame port was restored, the problem disappeared. Any ideas? Kevin Badeen Unix Administrator Harte-Hanks Response Management 512.434.5999 Tel 877.446.5548 Pag

1 0

Re: Systemic problems at Verizon
by Howard C. Berkowitz 16 Feb '01

16 Feb '01

>There exist little red caps that fit onto 66 blocks and binding >posts. They're hard to find, though. If someone here knows of >the supplier, I'll buy a few hundred. > >In the 60's there was a special red ty-wrap that went around/over >posts/punches for ""national security"" lines. You had to cut same >off to test, and {in theory} requisition a replacement. I've only >see same in BSP's so I've no idea if they ever got much use. I think the BSP called them Special Service Protection, and there was a more stringent version called Special Safeguarding Measures. The latter, IIRC, didn't quite qualify as a military grade Protected Wireline Distribution System, which went to the extents of pressurized conduit with intrusion detectors. > >We used to protect leased metallic pairs in a simpler manner; we >parked +130 Tip/-130 Ring on same. When Mr. Green put his butt set >on same; if his fingers didn't alert him, the BANG in his ear did. Someone did that once with _stranded_ wire, so the strand was fine enough to puncture the skin. I found myself in a corner with very little recollection of how I got there, and am really not sure that if there had not been a wall there, I would have kept going. Oh well...I didn't freeze to the conductor.

1 0

RE: happy bday IGS-R
by Martin, Christian 16 Feb '01

16 Feb '01

> I need something to route the Chaos protocols... :) > (leftover symbolics machines... :) > 3 points for knowing which was the last IOS rev that supports > Chaos protoocls. CHAOSnet support ended in SSR 9.2... ./chris

1 0

Re: Using unallocated address space
by smd＠clock.org 16 Feb '01

16 Feb '01

| could someone please explain the benefit of turning the registries into | internet police forces? Cool, speeding tickets for people with 10Gbps links in production today. We don't need a "police force" per se as much as a functionary who, on behalf of the paying membership of the registry, tries to establish (e.g., with a phone call! or some email!) whether the announcement is a question of simple, honest misconfiguration or misunderstanding, or whether it's deliberate. Moreover, with another couple of phone calls (or email), a deliberately bad announcer can talk with the network(s) immediately upstream from a deliberate bad-announcer and suggest that the membership as a whole would appreciate the installation of strict filters against the bad announcer. If that produces no results, rat out the source and its immediate upstreams to the whole membership. | and the offending party will announce 32 /23s.. what will this solve? Great, so we know that the offending party is not only deliberately announcing bogus data into the routing system, but actually _disrupting_ it. This is what real-life police are for. Sean.

2 1

RE: Systemic problems at Verizon
by Richard Welty 16 Feb '01

16 Feb '01

Jeff Mcadams <jeffm(a)iglou.com> wrote: > Also sprach Richard Welty > >it takes a very long time for an old ILEC to change, and i'd expect > >that tens or hundreds of mergers can take place without changing the > >behavior of the old line staff out in the field much at all. > I would somewhat contradict that. It hasn't taken GTE long at all to > adopt Bell Atlantic's anti-competitive ways with regard to > provisioning > DSL. i was thinking in terms of changing for the better. there is no question in my mind that the old NYNEX territory still sucks as much as it ever did, and the old Bell-Atlantic certainly deteriorated after the merger. richard

1 0

RE: happy bday IGS-R
by Paul Lantinga 16 Feb '01

16 Feb '01

Good thing all this is getting archived - it's cool to know some of what was happening out in the trenches back then. My IGS had a sticker on it that said, "Property of Stanford University". It was the router that UUNET placed at the now non-existent eit.com (Enterprise Integration Technologies) and came bundled with a massive rackmounted Cylink csu/dsu. The folks at Cylink thought that I was on crack when I called about a manual for it - the woman on the phone didn't even realize that Cylink had ever made them. Even better was when we changed providers to geo.net and tried to get UUNET to come pick up the router and csu/dsu. They were decidedly not excited about having it back in their inventory and refused to come and take it back. Anyway, it's hard to say who won the most points... most people got the GI reference and nearly everyone who responded privately had worked on rev's much older than what I have - ack! even version 6.x! Thanks to all for the thread. -Paul LANtinga Q9 Networks.

6 6

RE: Systemic problems at Verizon
by Richard Welty 16 Feb '01

16 Feb '01

Sean Donelan <sean(a)donelan.com> wrote: > Verizon is continuing to have network problems. ... > Are things as bad in Verizon country as they got in Ameritech country? > Eventually the various state PUC's had to intervene in Ameritech's > service problems. it would seem to vary depending on the ILEC/RBOC ancestry of various parts of Verizon. the old NYNEX (New York/New England) is bloody awful; the old Bell Atlantic (mid Atlantic) perhaps not so bad, and some of the old GTE-owned ILECs were not good at all. it takes a very long time for an old ILEC to change, and i'd expect that tens or hundreds of mergers can take place without changing the behavior of the old line staff out in the field much at all. richard

3 2