RE: [cobalt-users] Named Error in Secondary DNS

[Gerald Waugh <gwaugh@xxxxxxxxxxxxxxxxxxxxxxx>]

On Tue, 12 Mar 2002, Curtis Ross wrote:
> > You don't make dns records for a domain on the slave.
> > You only fill out the "perform secondary service for domain"
> > or some such nonsense. I don't use the GUI.
> > But all the slave needs is sn entry in /etc/named.conf for the domain (zone)
> > then it gets all it's info from the master.
> > You do need to go to the master and make the DNS records.
> 
> Right. That is what I do. But normally it creates a record in /etc/named with the info from the master.(sec.whateverdomain.com). This is not happening anymore.
> 

Look at /etc/named.conf  in both servers  (master / slave)
find the lines that have the domain on them.
The master
zone "test.com" { type master; file "pri.test.com"; };
The slave
zone "test.com" { type slave "sec.test.com"; };

another thing to check is that the slave knows who the master is

look at a nonworking zone file on the master pri.test.com;
===================================================
$TTL 86400
; BIND version named 8.2.3-REL Fri Feb  2 15:46:44 PST 2001
$ORIGIN com.
$TTL 86400
test  IN     SOA     fsn1.frontstreetnetworks.net. admin.fsntest.com. (
   2001041501    ; serial num
   10800         ;
   3600          ;
   604800        ;
   86400 )       ; Min TTL
   IN   NS   ns1.test.com
   IN   NS   ns2.test.com.

test.com.    IN      A       ip.ad.re.ss
www         IN      A       ip.ad.re.ss
===============================
Make sure both nameservers are in there.

increment the serial number (serial-number +1)
execute ndc reload test.com
execute tail -f /var/log/messages
look for the zone to load and notify slave
and for slave to ask fort XFER
--
Gerald Waugh