On Mon, Apr 16, 2012 at 11:35:04AM +0200, Chiesa Stefano wrote:
> I'm developing a web application to apply massive dns changes
> automatically.
> I have a master dns server and three slaves. To test the application I'm
> going to create an identical copy of the master server (in the same
> network too).
> What is scaring me is the update of the slaves. If I don't change
When testing, use different names. Make up your own top-level domain:
testing.stefano.
> anything in the Bind configuration on the test server at the first
> zone change it will replicate the zone to the slaves, and I,
> obviously, don't want it.
>
> What is the best way to stop ANY zone transfer (even to the slaves
> configured in the zones)?
> Is a global "NOTFY NO" enough?
allow-transfer { none; };
But the whole issue is moot if using a different name, or if the
testing host is not configured as a master to the slaves.
--
http://rob0.nodns4.us/ -- system administration and consulting
Offlist GMX mail is seen only if "/dev/rob0" is in the Subject:
_______________________________________________
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
