home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.protocols.tcp-ip.domains
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!uwm.edu!psuvax1!atlantis.psu.edu!barr
- From: barr@pop.psu.edu (David Barr)
- Subject: Re: CNAME records and MX/NS records
- Message-ID: <7b61Huh-_b@atlantis.psu.edu>
- Sender: news@atlantis.psu.edu (Usenet)
- Organization: Penn State Population Research Institute
- References: <1993Jan11.192147.8578@maths.tcd.ie> <1isteb$nmc@agate.berkeley.edu> <fn51H7&8_b@atlantis.psu.edu> <1iv1no$8mb@agate.berkeley.edu>
- Date: Tue, 12 Jan 93 18:49:09 GMT
- Lines: 31
-
- In article <1iv1no$8mb@agate.berkeley.edu> cliff@garnet.berkeley.edu (Cliff Frost) writes:
- >So, why do we find it useful to split out the nameservers' names like this?
- >
- >Well, we did it the second time we found ourselves faced with changing both
- >the names and addresses of our nameservers. It turns out that the process
- >becomes much easier if all you have to do is change or add addresses. Names
- >have a greater tendency to get hard configured into nooks and crannies than
- >IP addresses (although both do).
-
- Okay, I can sympathize with this. IMHO you'd be better off doing
- something like:
-
- fred.foo.bar. A 1.2.3.5
- betsy.foo.bar. A 1.2.4.5
- ns1.foo.bar. A 1.2.3.5
- ns2.foo.bar. A 1.2.4.5
-
- rather than:
-
- ns.foo.bar. A 1.2.3.5
- A 1.2.4.5
-
- Then you have the best of both worlds. Easy to reconfigure to a
- different name, as well as a different IP address. Also, you have an
- clearer distinction that the two addresses are indeed separate
- machines, not different interfaces on one machine.
-
- --Dave
- --
- System Administrator, Population Research Institute barr@pop.psu.edu
- What if there was no such thing as a hypothetical question?
-