home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip.domains
- Path: sparky!uunet!gatech!asuvax!ncar!woods
- From: woods@ncar.ucar.edu (Greg Woods)
- Subject: Re: navy.mil gone?
- Message-ID: <1992Aug21.192244.20388@ncar.ucar.edu>
- Organization: Scientific Computing Division/NCAR Boulder, CO
- References: <1992Aug18.143937.24042@ncar.ucar.edu> <23928@oasys.dt.navy.mil>
- Date: Fri, 21 Aug 1992 19:22:44 GMT
- Lines: 28
-
- In article <23928@oasys.dt.navy.mil> tinker@oasys.dt.navy.mil (Robert Tinker) writes:
- > I think "navy.mil" is only a placeholder in the root servers, i.e
- > there are no global navy.mil nameservers. These exist one level down.
-
- Several other people told me this, so I went ahead and ran some tests for
- the particular second-level domain in question (noarl.navy.mil).
-
- $ host -t any noarl.navy.mil c.nyser.net
- Using domain server:
- Name: c.nyser.net
- Address: 192.33.4.12
- Aliases:
-
- noarl.navy.mil NS TURNER-JOY.NOARL.NAVY.MIL
- noarl.navy.mil NS MADDOX.NOARL.NAVY.MIL
- $ host -t any noarl.navy.mil ns.nic.ddn.mil
- Using domain server:
- Name: ns.nic.ddn.mil
- Address: 192.112.36.4
- Aliases:
-
- $
-
- Note that one root server has information about this domain, another
- does not. Inconsistency between the root servers. It is clear that this
- is where my problem is stemming from.
-
- --Greg
-