Automatic refresh secondary when primary change

[Dave Clark]

I've seen refused notifies before and the problem was the NS records were
incorrect.  You could try verifying that your NS records refer to all of the
dns servers and that those dns server domains point to the right IPs.  You
say it is your external view that is having the problem - and that is
something we can debug ourselves if you provide the real domain.

The reason only the external view and not the internal view might be working
may be because you have this in your options block:

>        allow-notify {
>                ip-secondary;
>        };

And ip-secondary only mentioned the private IPs and not the external IPs.
But if you have correct NS information then you won't need allow-notify at
all.

Dave

----- Original Message ----- 
From: "Sim" <simvirus at gmail.com>
To: <bind-users at isc.org>
Sent: Wednesday, February 01, 2006 10:51 AM
Subject: Re: Automatic refresh secondary when primary change


> > You need to turn on notify. In named.conf you can do this globally in
> > options by adding:
> >
> > notify yes;
>
> Hi!
>
> I have enabled it on secondary ( primary was active ) and add :
>
>        allow-notify {
>                ip-secondary;
>        };
>
> because whitout this on secondary, it show:
>
> /var/log/named/info
> <<< refused notify from non-master: secondary#32782 >>>
>
>
> Now I can see this in secondary:
>
> Feb  1 16:41:37 ns2 named[6129]: zone xxxxxx.com/IN/internal-in:
> Transfer started.
> Feb  1 16:41:37 ns2 named[6129]: transfer of 'xxxxxx.com/IN' from
> master#53: connected using secondary#56435
> Feb  1 16:41:38 ns2 named[6129]: zone xxxxxx.com/IN/internal-in:
> transferred serial 2006020105
> Feb  1 16:41:38 ns2 named[6129]: transfer of 'xxxxxx.com/IN' from
> master#53: end of transfer
> Feb  1 16:41:38 ns2 named[6129]: zone xxxxxx.com/IN/internal-in:
> sending notifies (serial 2006020105)
>
>
> , but I have the some problem :(
>
> I need to reload bind manually or wait ...
>
> Thanks!
>
>
>