*BSD News Article 70913


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.ecn.uoknor.edu!solace!nntp.uio.no!news.cais.net!nntp.primenet.com!news.mathworks.com!newsfeed.internetmci.com!news1.emplink.net!news
From: Richard Heaton <rheaton@empac.com>
Newsgroups: comp.unix.bsd.bsdi.misc
Subject: Re: named help...
Date: Thu, 13 Jun 1996 18:28:42 -0700
Organization: Empac International
Lines: 55
Message-ID: <31C0C04A.167EB0E7@empac.com>
References: <4pnmi5$3a7@agate.nbnet.nb.ca>
NNTP-Posting-Host: salmon.empac.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Mailer: Mozilla 3.0b4Gold (X11; I; BSD/386 uname failed)
CC: cavenerl@nbnet.nb.ca, rheaton@empac.com

Lance Cavener wrote:
> 
>  Just wondering.. I set up my DNS daemon with all the aliases for my
> system, and I added the IP addresses for my secondary servers
> (config_dns) so everything should work.. Anyway, how do the secondary
> servers (and every other DNS server in this world) know that I created
> thoes aliases?
> 
>  Thanks,
>  Lance Cavener


The secondaries need to be set up to look at your primary to do a zone transfer . Basically,
in your /eetc/named.boot on the primary, you will have lines like:

directory /etc/namedb
primary domain1 zone-file1
primary domain2 zone-file2
...

then each file /etc/namedb/zone-file* will contain the RR for that domain. You may want to
add NS records at the top of each zone file (under the SOA) pointing at your secondaries

Then , on each secondary, the /etc/named.boot file will have lines like:

secondary domain primaryip1 primaryip2 ...

where primaryip* is the ip address of the primary source for zone information (ie the
primary). Now, type /usr/sbin/ndc restart on each machine (or reboot) and the zone transfers
should take care of the rest.

Basic idea of primaries and secondaries is that, for any queries, both can answer with
authority, but it makes admin easier since the zone info is centralized on the primary and
distributed by named to the secondaries. 

Note: the SOA contains a field "Serial" when you make change to a zone-file (on the primary
:-) ) increment it. This tells named that it is a new(er) record than the one in its cache.
Use /usr/sbin/ndc reload to force a zone transfer and cache update on both primaries and
secondaries.

Hope this helps. The Nutshell Handbook 'DNS and BIND' is very useful.
Rich


-- 
rheaton@empac.com
System Engineer,Program Manager
EMPAC International
Fremont,California
http://www.empac.com

"A fanatic is one who can't change his mind 
and won't change the subject."

          -Winston Churchill