On Tue, 2009-11-03 at 13:34 -0500, James B. Byrne wrote:
zone "byrnejb.ca" { type slave; masters { 216.185.71.33; }; file "/var/named/slaves/byrnejb.ca.hosts"; };
Which is, as far as I can see, identical.
In any case, the real problem is that neither slave actually transfers the updated zone file and I cannot figure out why not. I have verified that the master zone file serial number is greater than that of the slave zones.
So, I have two questions:
- Why is the source address 216.185.71.27 when the bind named
listens on 216.185.71.33 and answers queries from the same address. Admittedly, 216.185.71.33 is a virtual ip hosted on 216.185.71.27 but we have been doing this for over a decade now and I have never seen this behaviour before.
- Why are the notifies ignored? Again, we have had this set up for
over a decade and none of these problems until now, and the only thing that has happened on the dns side of things recently were the CentOS updates last week.
I am not a DNS specialist, I set this up several years ago and I am perplexed as to why it is now giving me these difficulties. Any help would be gratefully appreciated.
---- why not add the other ip address just in case on the slaves...
masters { 216.185.71.33; 216.185.71.27; };
you might also want to specifically add them to allow update...
acl HLLmasters { 216.185.71.33; 216.185.71.27; };
allow-update { HLLmasters; };
Craig