help with notify-source

tony z tzucc at yahoo.com
Tue Mar 25 02:16:50 UTC 2008


Hopefully my other post will get approved .. it shows my named version, and the named.conf... 
I have logs from my backup DNS which shows the slave DNS refusing notify's from my other IPs on the master DNS server... then eventually the right master IP sends the notify, and the AXFR proceeds and completes normally. Do you expect BIND to rotate it's NOTIFYs through various IPs on the multihomed server like this?

Barry Margolin <barmar at alum.mit.edu> wrote: In article , tony z  wrote:

> I have a BIND 9.x server with multiple ethernet interfaces and IPs.

What's the value of x?

> I need the NOTIFY messages to go out on a specific IP, because I am using 
> TSIG updates
> to my slave and that slave will not accept a TCP NOTIFY connection from any 
> other than one of
> my specific IPs.
> I put a notify-source directive inside my zone files and options area, but 
> nothing seems to work.
> BIND/named seems to randomly rotate through all my IPs sending NOTIFY, until 
> it uses the IP
> that my slave wants to hear from, and then the transfer from master to slave 
> happens. But this takes like hours.
> Does notify-source actually work, or am I using the wrong directive or using 
> the right directive in the wrong manner.

Post your named.conf.

-- 
Barry Margolin, barmar at alum.mit.edu
Arlington, MA
*** PLEASE don't copy me on replies, I'll read them in the group ***






More information about the bind-users mailing list