View Single Post
  #1  
Old 18th January 2007, 18:57
martinfst martinfst is offline
Senior Member
 
Join Date: Dec 2006
Location: Hilversum, The Netherlands
Posts: 880
Thanks: 1
Thanked 18 Times in 17 Posts
Send a message via MSN to martinfst Send a message via Skype™ to martinfst
Default Bind 9.3 - secondary DNS changed behaviour

Have it 'all' running, but I found an error in my syslog file, which I wanted to try to fix first, but I don't know where to look in the php scripts, so I'll post it here for the more experienced developers.

The error I have is:
Code:
Jan 18 17:24:37 xxxxxx02 named[1041]: zone xxxxx.tld/IN: refused notify from non-master: nn.nn.nn.nn#32780
This is when I restart Bind on the server that runs the secondary DNS server for my domain.

After googling, I think this is caused by a change per Bind 9.3, so pretty recent. I am running 9.3.2. I tried the allow-notify directive with no luck. The only solution that removed the error is to add notify off to the specific section of the slave DNS server, so that it (/etc/bind/named.conf) looks like:
Code:
zone "xxxxxx.tld" {
        type slave;
        file "sec.xxxxxx.tld";
        masters { nn.nn.nn.nn; };
        notify no;
};
I tried to find in the scripts where I could add this as a default addition when creating a new slave, but using 'grep -ir <some identifier string> /root/ispconfig' or grep -ir <some identifier string> /home/admispconfig' did not bring forward a proper hit. May I suggest to add the 'notify off' directive standard to a slave entry?

Edit: added filename of the bind config file, where this directive should be placed.

Last edited by martinfst; 18th January 2007 at 19:00.
Reply With Quote
Sponsored Links