Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!ukma!david From: david@ms.uky.edu (David Herron -- One of the vertebrae) Newsgroups: comp.mail.uucp Subject: Re: .US domain map entries incorrect Keywords: .US domain, map Message-ID: <10357@s.ms.uky.edu> Date: 12 Oct 88 15:44:03 GMT References: <537@comdesign.CDI.COM> Reply-To: david@ms.uky.edu (David Herron -- One of the vertebrae) Organization: U of Kentucky, Mathematical Sciences Lines: 31 [to summarize .. Geoff is complaining because fernwood...us doesn't have a line saying "fernwood .fernwood...us". The article I am replying to asks why you'd want such a thing in the first place since fernwood...us isn't a domain, it's a host.] Why *wouldn't* you want such a thing? I recently received a piece of mail from Erik Fair asking why I didn't have a line "ukma=e.ms.uky.edu" in the ukma entry. But what would be the point of that? I have a gateway announced for BOTH .ms.uky.edu AND .uky.edu (as well as .ms.uky.csnet and .uky.csnet), so if others' software is functioning correctly (i.e. taking advantage of my gateway declaration) the routes generated will go to the right place when given "e.ms.uky.edu". To get back to the original question ... declaring the gateway *does* handle the routing for fernwood...us. In *addition* it gives you the flexibility of having other hosts 'under' the fernwood name. If there is to be a difference between domains and host names, why isn't the difference made explicit in the way they are represented? I put forward that since the representation is the same in either case, then neither human nor software is able to tell a difference. If there is no difference, then they are the same thing. -- <-- David Herron; an MMDF guy <-- ska: David le casse\*' {rutgers,uunet}!ukma!david, david@UKMA.BITNET <-- <-- "Smarter than the average pagan god ... "