bad zone not loaded

Bob Harold rharolde at umich.edu
Tue Feb 3 14:44:34 UTC 2015


Two suggestions:
1. Don't stop/start named.  Instead, do "rndc freeze", update the zone
files, "rndc thaw", "rndc reload".  If a zone is bad, I think BIND will
continue to server the old zone.  Also there is no break in service since
BIND is never stopped.

or more complicated:
2. Have your provisioning system update a hidden master DNS server, and
have the DNS server that others see be a slave.  Only valid zones will
transfer to the slave.



-- 
Bob Harold
hostmaster, UMnet, ITcom
Information and Technology Services (ITS)
rharolde at umich.edu
734-647-6524 desk

On Tue, Feb 3, 2015 at 8:43 AM, hugo hugoo <hugobxl at hotmail.com> wrote:

> Hello,
>
> Can anybody help me?
> I am using bind 9.8.2
>
> Sometime my provisionning system provision a bad record ina zone.
> Example A record with 1.2.3.4.5 value (just an example).
>
> My provisioning system do not detect  all bad situations and therefore I
> can have a zone with only a bad record.
>
> This zone is not updated with a reload (this is OK)...but the whole zone
> is no more loaded after a stop/start.
>
> Is it possible to tell BIND to reload all correct records and just discard
> the bad record from the zone?
> I can only give the parameter "DISABLE_ZONE_CHECKING" = yes in order that
> BIND starts.
>
>
> Thanks in advance for your feedback,
>
> _______________________________________________
> Please visit https://lists.isc.org/mailman/listinfo/bind-users to
> unsubscribe from this list
>
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20150203/c2e969a0/attachment.html>


More information about the bind-users mailing list