master and slave zone..

[Joseph S D Yao]

On Wed, Jul 12, 2000 at 01:12:00PM -0400, unknown wrote:
> 
> on ns1 server i have following in /etc/named.conf
> zone "spde.com" {
>         type master;
>         allow-update { none; };
>         allow-transfer { 63.251.19.66;63.251.19.67;63.251.19.68; };
>         file "spde.com";
> 
> };
> 
> on ns3 server i have following in /etc/named.conf
> zone "spde.com" {
>         type slave;
>         master { 63.251.19.66; };
>         file "spde.com";
> };
> 
> after i update zone on ns1 in /var/log/messages i got the following
> Jul 12 10:26:50 ns1 named[11195]: Sent NOTIFY for "spde.com IN SOA"
> (spde.com); 2 NS, 2 A
> 
> on ns3 in /var/log/message i got the following:
> Jul 12 10:46:36 tucows named[25021]: rcvd NOTIFY(spde.com, IN, SOA) from
> [63.251.19.66].1040
> Jul 12 10:46:36 tucows named[25021]: rcvd NOTIFY for "spde.com", name not
> one of our zones

What a garish .sig [omitted].  ;-}

In the above, did you pick and put the text, or is there a possibility
that one of the names is spelled incorrectly?

After you had put the zone into named.conf on ns3, did you restart the
'named'?  IIRC, a 'reload' won't do.

Is ns1 .66?  If so, why does it have itself listed in the
allow-transfer clause?

This is not meant to insult your intelligence, but you had not
mentioned any of these things.

-- 
Joe Yao				jsdy at cospo.osis.gov - Joseph S. D. Yao
COSPO/OSIS Computer Support					EMT-B
-----------------------------------------------------------------------
This message is not an official statement of COSPO policies.