Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!apple!agate!garnet.berkeley.edu!cliff From: cliff@garnet.berkeley.edu (Cliff Frost) Newsgroups: comp.protocols.tcp-ip.domains Subject: Re: Creating a domain alias Message-ID: <1991Mar25.192653.28803@agate.berkeley.edu> Date: 25 Mar 91 19:26:53 GMT References: <1461@lehi3b15.csee.Lehigh.EDU> Sender: usenet@agate.berkeley.edu (USENET Administrator) Reply-To: cliff@garnet.berkeley.edu (Cliff Frost) Distribution: comp Organization: ucb Lines: 29 In article , Kimmo.Suominen@lut.fi (Kimmo Suominen) writes: ... |> |> Is it really correct to have two names pointing to the same address. Why not? It may be harder to maintain consistency in your database, but if you want to do it I don't see why not. |> The way I see it, one of these names should be a CNAME entry. Imagine a host with multiple interfaces. You might like to be able to say "telnet host" and have telnet try all the interfaces. But you might also like to be able to say "telnet host-ether" and have telnet try only one of the possible interfaces. Imagine you have services running on multiple machines (maybe some have multiple interfaces). Your nameservers might be NS.domain, your FTP repositories might be FTP.domain, etc. If you want to control which machines/interfaces get used for these services you may have to assign addresses to each service-name. I believe that what is restricted is that each ADDRESS can have only one PTR record. That is, each ADDRESS has one canonical name. But, many names can use the same address. Cliff Frost UC Berkeley