This summary encompasses two questions about DNS. The questions had to
do with:
A) One machine serving as primary for tow different domains
B) Maintaining the names of machine@domain after the machines have been
moved to machine@sub.domain.
============================ Original Query #1 ===============================
Is anyone running DNS such that a single name server is the primary for
more than one domain ?
If so could you tell me how you set that up ?
Does the named.boot file simply have something like:
primary domain-1 named.hosts
primary domain-2 named.hosts
and then you put all the different machines into named.hosts as fully
qualified domain names ?
What about pointer records are they necessary ?
I am faced with having to be the primary for the cch.com and ca.cch.com
domain and I am not too sure how to go about doing on a single machine.
I would rather not have more than one primary machine, for various
reasons.
===============================================================================
As it turns out the only thing that is really required here is separate
zone and zone rev files for each domain as well as the appropriate
entries in the named.boot file.
IMHO the easiest way to accomplish this dual domain with one primary
scenario is to formulate a set of DNS files for each domain and then
just combine the entries from the boot files into a single file.
For example:
In my case I am dealing with cch.com and ca.cch.com so the boot file
would appear as.
primary cch.com named.hosts
primary ca.cch.com named.ca.hosts
primary xxx.xxx.xxx.in-addr.arpa rev.netxxx
primary yyy.yyy.yyy.in-addr.arpa rev.netyyy
Now comes the tricky part.
While the above is a simple solution, my particular situation was
complicated by the fact that the machines in cch.com all had to be
moved to ca.cch.com BUT certain machines had to be maintained, at least
as aliases, within the original cch.com domain.
So, I had not only to maintain a single machine as primary for two
domains but also to maintain the same machines with different names in
both domains. This led to posting #2.
============================ Original Query #2 ===============================
I have just recently changed our domain name from cch.com
to ca.cch.com. That all was fine, however I need to maintain
aliases for a couple of the machines such that their names
use the old domain name.
For example:
What used to be:
machine@cch.com
is now:
machine@ca.cch.com
But I need to maintain an alias for machine such that the
machine will still be known as:
I have been told that in the CA.CCH.COM zone file I cannot
have something like:
machine.cch.com. IN A xxx.xxx.xxx.xxx
But putting something like:
machine IN A xxx.xxx.xxx.xxx
machine.cch.com. CNAME machine.ca.cch.com
is illegal.
===============================================================================
As it happens, matters were being confused by the fact that one machine
was acting as primary for both ca.cch.com and cch.com. As a result, the
information in the zone files would interact to make it appear that
illegal data was present in the files.
The solution to the problem was provided by dave barr
( barr@pop.psu.edu ). Basically all that is needed is CNAME records in
the cch.com domain that point at the ca.cch.com subdomain thusly.
machine1.cch.com. in cname machine1.ca.cch.com.
machine2.cch.com. in cname machine2.ca.cch.com.
This would in effect cause a lookup for machine1.cch.com to be halfway
resolved to the name of the machine in the ca.cch.com subdomain.
A query would be sent to the domain server for the ca.cch.com
subdomain for final resolution.
For mail delivery to be effected to the subdomain machines that are
listed as CNAME records in the parent domain, an entry as below would
also be needed.
- In the parent's zone file
cch.com. in mx mailhost.ca.cch.com.
- In the subdomain's zone file.
machine1.ca.cch.com. in a xxx.xxx.xxx.xxx
machine1.ca.cch.com. in mx mailhost
machine2.ca.cch.com. in a xxx.xxx.xxx.xxx
machine2.ca.cch.com. in mx mailhost
Many thanks to those who responed:
Todd Kover <kovert@cs.UMD.EDU>
john@oncology.uthscsa.edu (John Justin Hough)
fabrice@pure.com (Fabrice Guerini)
stlee@patch.tandem.com
cecilp@vancouver.cantel.rogers.com (Cecil Pang)
Piete Brooks <Piete.Brooks@cl.cam.ac.uk>
jason andrade <jason@pest.ctpm.uq.oz.au>
Dallas N Antley <dna@clas.ufl.edu>
Richard Butler <richard@biocell.irmkant.rm.cnr.it>
Claude Marinier <MARINIER@emp.ewd.dreo.dnd.ca>
steve@gec-epl.co.uk (Steve_Kilbane)
mhill@lesol1.dseg.ti.com (Mike Hill)
fabrice@cisk.ATMOS.Ucla.EDU (Fabrice Cuq)
rwolf@dciem.dnd.ca (Robert Wolf)
john@oncology.uthscsa.edu (John Justin Hough)
js@iok.unit.no
begourd@amoco.com (Bruce Gourd)
Eamonn.McGonigle@compapp.dcu.ie
Jaap Bril <Jaap.Bril@ice.nl>
David Barr <barr@pop.psu.edu>
R._Scott_Bailey.wbst300@xerox.com
stuart@TO.Mobil.COM (Stuart Pearlman - RDR)
Wed Mar 2 05:11:51 EST 1994
===========================================================================
Larry Chin {larry@cchtor.ca.cch.com} CCH Canadian Ltd.
System Administrator 6 Garamond Court
Research and Development North York, Ontario.
(416) 441-4001 ext. 349 M3C 1Z5
===========================================================================
Death is nature's way of telling you to slow down
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:08:57 CDT