Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!ub.d.umn.edu!cs.umn.edu!thelake!steve From: steve@thelake.mn.org (Steve Yelvington) Newsgroups: comp.mail.uucp Subject: Re: Re: Who pays the bill? Message-ID: Date: 1 Aug 90 05:56:32 GMT References: <26A738A8.725B@tct.uucp> Organization: Otter Lake Leisure Society Lines: 25 X-Member-Of: STdNET X-Bad-Pun: There's no place like Nome for the Hollandaise. [In article , bob@MorningStar.Com (Bob Sutterfield) writes ... ] > ... To have a domain implies by definition that it is registered. > Until a DNS query of NS.NIC.DDN.MIL returns the correct sort of > information, "foo.com" is just a string of characters, not a domain. > And yes, people construct silly strings of characters all the time - > just read news.groups :-) This leads to something I've been wondering about: What about third- and greater-level domains, as in "bozo.foo.com"? Is there a need for them to be registered? The reason I ask is that I have one such site, within the registered .mn.org domain, but not individually listed in the nic.ddn.mil database. (I've looked.) I have seen that mail to thelake.mn.org from Internet sites sometimes fails with error messages indicating that there is no such domain. But I thought that one of the big advantages of having a qualified, registered domain was that multiple sites could be served with a single listing. -- Steve Yelvington at the (rain-replenished) lake in Minnesota steve@thelake.mn.org