Automatic updates to internal views of slave zones?

Jaap Winius jwinius at umrk.nl
Fri Dec 24 23:31:55 UTC 2010


Quoting Mark Andrews <marka at isc.org>:

> You can just have the internal view transfer from the external view.
>
> key external {
> 	....
> };
>
> view internal {
> 	match-clients { !key external; 127.0.0.1; .... };
> 	zone xxx {
> 		type slave;
> 		masters { 127.0.0.1 key external; .....};
> 		file "internal/xxx";
> 	};
> };
>
> view external {
> 	match-clients { key external; any; };
> 	zone xxx {
> 		type slave;
> 		masters { .... };
> 		file "external/xxx";
> 		notify explict;
> 		also-notify { 127.0.0.1; };
> 		allow-transfer { key external; .... };
> 	};
> };

This configuration works, but seems to have one drawback: the "notify  
explicit" statement appears to have no effect. Instead, in this case  
it works like the default, "notify yes." Consequently, soon after this  
slave receives a NOTIFY message from the master, it proceeds to send   
NOTIFY messages to all the other slaves, including the localhost, each  
time resulting in numerous "refused notify from non-master" errors  
that shows up in the logs.

Is there a way to prevent this behavior -- to get "notify explicit" to  
work the way it usually does -- or is this a bug?

Thanks,

Jaap



More information about the bind-users mailing list