home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip.domains
- Path: sparky!uunet!wupost!ukma!psuvax1!atlantis.psu.edu!barr
- From: barr@pop.psu.edu (David Barr)
- Subject: Re: how to look up certain top-level domains at nic.ddn.mil?
- Message-ID: <d+z1H*k4i9@atlantis.psu.edu>
- Sender: news@atlantis.psu.edu (Usenet)
- Organization: Penn State Population Research Institute
- References: <1992Sep6.155944.22695@magnus.acs.ohio-state.edu> <1992Sep7.141746.27919@ennews.eas.asu.edu>
- Date: Mon, 07 Sep 92 19:13:57 GMT
- Lines: 37
-
- In article <1992Sep7.141746.27919@ennews.eas.asu.edu> sridhar@enuxhb.eas.asu.edu (Sridhar Venkataraman) writes:
- >pjd@magnus.acs.ohio-state.edu (Peter J Dotzauer)
- >writes on comp.protocols.tcp-ip.domains:
- >
- >)The general syntax for looking up top-level domains appears to be
- >) whois -h nic.ddn.mil xx-dom
- >)where xx is the top-level domain.
- >)But this pattern is inconsistent, since there is no 'yu1-dom' or
- >)'co1-dom'.
- >
- >The command line clients work for all the whois options available by
- >telnetting to NIC. In your case,
- >
- >whois -h nic.ddn.mil "domain xx"
- >seemed to get the matches and
- >whois -h nic.ddn.mil "!su1-dom"
- >got the right match.
-
- Isn't this exactly what he said? Thank you for restating the obvious
- without giving a solution. He wasn't asking _how_ to get the answer,
- he was asking _why_ is it inconsistent.
-
- It doesn't appear that there is a solution to the original problem,
- although it seems as though there _should_ be. Perhaps a new qualifier
- instead of "domain", called "topdomain". So:
-
- whois "topdomain edu"
- whois "topdomain su"
-
- would be guaranteed to be unique. (why force people to query the NIC
- twice when there should be a way to get what you want once?)
-
- --Dave
- --
- System Administrator, Population Research Institute barr@pop.psu.edu
- Contains: Carbonated water, high fructose corn syrup and/or sugar, caramel
- color, phosphoric acid, caffeine, citric acid and natural flavorings.
-