Clarification about DNS notify
list at sheringeorge.co.cc
Fri Sep 10 08:12:00 UTC 2010
Thanks for looking into this.
Basically, my previous question came from my ignorance. But, I learned
more and I think found the answer.
"The SOA MNAME field is used by NOTIFY and by dynamic update.
Authoritative name servers send NOTIFY messages to all name servers in
NS records that aren't in the MNAME field, and dynamic updaters try to
send updates to the name server listed in the MNAME field first, if
it's also listed in the NS records for the zone."
I could confirm that most of the zones are configured such that
serverB will receive NOTIFY as per above statement. So, if above
statement is correct, I am with my answer :)
Thank you so much for your help :)
>> A wild guess would be that you're missing a "notify no" or "notify
master-only" option on your slave servers.
I have verified that "notify no" or "notify master-only" are not used
in my named.conf file.
On Fri, Sep 10, 2010 at 1:26 PM, Torsten <toto at the-damian.de> wrote:
> Am Fri, 10 Sep 2010 12:51:11 +0530
> schrieb Sherin George <list at sheringeorge.co.cc>:
>> Hey Guys,
>> I have an issue which need some help.
>> I have two master DNS servers, say A & B.
>> A is running freebsd & B is running centos. B is running BIND 9 also.
>> Now, I want to add one more to this cluster say C.
>> I have installed centos in C with BIND 9. Now, I have copied
>> /etc/named.conf & /var/name from B to C. Now I restarted named in C.
>> Everything worked.
>> Now, I have a question which may be quite simple, but I couldn't find
>> an answer even after lot of googling. So, I would be extremely
>> grateful for any advice you could offer.
>> When I restarted named in C, I could see that C is sending DNS
>> notifications and B is receiving it
>> from /var/log/messages in C:
>> "Sep 9 23:53:44 serverC named: zone example.com/IN: sending
>> notifies (serial 20050 30401)"
>> from /var/log/messages in B:
>> Sep 9 23:53:44 serverB named: client XX.XX.XX.XX#54546:
>> received notify for zone 'example.com'
>> I checked /etc/named.conf and I couldn't see any particular reason
>> for C choosing to notify B.
>> Any explanation to this behavior or a link to any relevant guide will
>> be helpful.
> Sharing your current configuration would help in helping you with your
> problem. ;)
> A wild guess would be that you're missing a "notify no" or "notify
> master-only" option on your slave servers.
>> bind-users mailing list
>> bind-users at lists.isc.org
More information about the bind-users