Many thanks for your help.
I will focus now on my provisionning system.
> Date: Wed, 4 Feb 2015 08:42:40 -0500
> From: a...@clegg.com
> To: bind-users@lists.isc.org
> Subject: Re: bad zone not loaded
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> On 2/3/1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2/3/15 8:43 AM, hugo hugoo wrote:
> Sometime my provisionning system provision a bad record ina zone.
> Example A record with 1.2.3.4.5 value (just an example).
The point of a provisioning system is to keep this type of problem
from happening.
In message , hugo hugoo writes:
>
> 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
Bob Harold wrote:
> 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
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 provisi
On 03.02.15 13:43, hugo hugoo wrote:
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 wi
6 matches
Mail list logo
