Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!uakari.primate.wisc.edu!sdd.hp.com!spool.mu.edu!agate!ucbvax!VM1.ULG.AC.BE!PIRARD From: PIRARD@VM1.ULG.AC.BE (Andr'e PIRARD) Newsgroups: comp.protocols.tcp-ip Subject: re: name handling in DNS resolvers Message-ID: <9105211817.AA02365@ucbvax.Berkeley.EDU> Date: 21 May 91 14:37:19 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Organization: University of Liege (Belgium), SEGI (Computing Center) Lines: 17 >Ahh, but most recursive searching resolver libraries can be forced not to >append successive domains by anchoring the name with a period. I'd put it the other way, viz: 1) The naive user types full x.y.z canonical names. 2) The more understanding may drop any level of his own host name with, typed on host myhost.dpt1.domain : x. giving x.dpt1.domain x.dtp2.. x.detp2.domain etc... 3) Nothing left to chance, no more name servers resolving single labels to local host name, nothing to do with the guru's 1035 dots convention etc... And I don't like the idea of the host file serving nicknames' purpose. Nicknames are often personal and the user should be able to maintain its own, mapping to full names and not addresses. A host file doesn't do that. Finally, it's sorry that making these kinds of subjects an implementation issue produces such various user interfaces.