BIND 9.2.4 NOTIFY problem from Master

[Meadows, Marty]

Sorry about all this e-mail.


1)      I see that I should have been sending to bind-users not bind10-users

2)      I see that I should have been using allow-notify on my secondaries

Problem solved.




From: bind10-users-bounces+marty.meadows=hp.com at lists.isc.org [mailto:bind10-users-bounces+marty.meadows=hp.com at lists.isc.org] On Behalf Of Meadows, Marty
Sent: Monday, September 27, 2010 10:55 AM
To: bind10-users at lists.isc.org
Subject: RE: BIND 9.2.4 NOTIFY problem from Master

I did a search of the bind-users archive and came up with this text from Matt:

"Notify messages are ignored unless they come from a expected
source (the addresses in the masters clause or in the allow-notify
acl).

Either list all the master's addresses in the masters clause,
force the master to use a specific address (notify-source) or
add the masters alternate addresses to the allow-notify acl
for the zone."

The only thing I'm a little confused about now is the "notify-source" directive. Not sure how to get it to accept multiple IP addresses. The syntax as I view it doesn't seem to make that an option.

Marty



From: bind10-users-bounces+marty.meadows=hp.com at lists.isc.org [mailto:bind10-users-bounces+marty.meadows=hp.com at lists.isc.org] On Behalf Of Meadows, Marty
Sent: Monday, September 27, 2010 9:49 AM
To: bind10-users at lists.isc.org
Subject: BIND 9.2.4 NOTIFY problem from Master


Following a reboot of our Master BIND server a few days ago we noticed that "automatic" zone file updates on the secondary BIND servers began failing.



The secondaries can be reloaded manually with an rndc reload. They will automatically refresh zone files every 4 hours as defined in the

SOA record. They receive notification from the Master but they appear to ignore it. Why?



These BIND instances are running on Solaris 10 platforms.

These BIND servers are multi-homed with IP addresses on a 143.242 and a 10.1 network.



We know the secondaries receive notification of zone file changes because we've turned on the notify category in our logging channel statement.

Thanks very much for any advice or assistance you can offer.
Marty

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind10-users/attachments/20100927/b485232c/attachment.html>