Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!elbereth.rutgers.edu!ron.rutgers.edu!ron From: ron@ron.rutgers.edu (Ron Natalie) Newsgroups: comp.protocols.tcp-ip Subject: Re: Domain resolver resets needed Message-ID: Date: 23 Mar 89 16:03:12 GMT References: Organization: Rutgers Univ., New Brunswick, N.J. Lines: 37 Kieth: There's a simple solution to this. Walk around to the back of your PSN and swap the cables for the TAC and your host. This gratuitous renumbering on the MILNET is one of the silliest things I've seen in years. It was a hold over from the old days (when TIP's were integral with the IMPs) that TAC's occupied port 2. The displacing of every host on the MILNET who occupy port zero is a real pain. I notice that either the NIC didn't get bumped, or their nameserver info is out of date. Of course this is from the people who brought you the quaint phrase "rehomed" as a description of what they did when they kicked most of the universities off the ARPANET last year. This from the same group that wastes more time on the Domain transition issue thinking up what to name the hosts than actually doing anythign about it. Several years ago when I was still in the employ of the Army, and one of the only representives of an actual military site on the Internet Engineering Task Force, we sat down with a subcommittee to figure a way to practically make the domain transition for the military nodes. The recommendation involved things like setting up a first step with a few nameservers that had the authoritative information for the .MIL domain, and would forward domain queries for less adventuresome MILNET sites. I was probably sufficiently cautious because at the time I deplored the domain implementation (is this any way to run a distributed database). All of these recommendations were ignored. The next debacle was the demise of the interim .ARPA domain. People seemed to think that the magical removal of this domain was going to accomplish something. To me it's just another top level domain, nor more or less valid than .GOV or .MIL or anything else. What needed to be done is to convince the military sites to do name resolution, or to at least fake it well. Just renaming the hosts did nothing to help this and we're still in the dark ages where it comes to talking to the guys on the Autodin II side of the universe. -Ron (Blown to hell by BRL) Natalie