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; };
        [COLOR="DarkRed"]notify no;[/COLOR]
};

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.

 

If I remember corectly the template file is locates at

Code:

/root/ispconfig/isp/conf/named.conf.master

 

That's exactly it! Thanks. Modified the template and it all works like a charm. Should be easy to implement in the next version of ISPConfig.

Code:

<!-- BEGIN DYNAMIC BLOCK: named_slave -->
zone "{DOMAIN}" {
        type slave;
        file "sec.{DOMAIN}";
        masters { {MASTERS}; };
        notify  no;
};
<!-- END DYNAMIC BLOCK: named_slave -->

Oops, what did I say? No, no! 1st I have to do some work on cert generation of the ispconfig httpd server...........