In message <6134bb3286a31d4db61e57114e8ba7c0609bf...@seaembx01.olympus.f5net.co
m>, Jack Tavares writes:
> Mark:
>
> >Ignore them. They are from the built in empty zones. They are fixed in
> >the next maintenance release.
>
> I notice that adding
> "enable-empty-zones no;"
>
> to the config s
On Mar 26, 2012, at 11:30 AM, Carlos Ribas wrote:
> Hello all,
>
> I accidentally changed the serial number to one bigger than 32 bits and now
> I'm trying to reset the serial number. Following the manual of Bind9 I tried
> to add 2147483647 (2ˆ31-1) to the number and reload the server, but my
On Mar 23, 2012, at 10:54 AM, Eric Chandler wrote:
> I have a question with regards to ordering of masters in slave zones. In the
> example below, will the slave zone try these in order each and every time?
> [...] or does it choose at random?
Masters are tried in the order listed.
Regards,
Mark:
>Ignore them. They are from the built in empty zones. They are fixed in
>the next maintenance release.
I notice that adding
"enable-empty-zones no;"
to the config stops these messages.
Is there any downside to doing that?
Thank you
--
Jack
___
In message <6134bb3286a31d4db61e57114e8ba7c0609bf...@seaembx01.olympus.f5net.co
m>, Jack Tavares writes:
> Hello
>
> I get several errors whenever I run rndc reload
> that look like this:
>
> named[9178]: 27-Mar-2012 05:56:00.798 general: error: zone 0.IN-ADDR.ARPA/IN/
> view_internal_dns: zone
Hello
I get several errors whenever I run rndc reload
that look like this:
named[9178]: 27-Mar-2012 05:56:00.798 general: error: zone
0.IN-ADDR.ARPA/IN/view_internal_dns: zone serial unchanged. zone may fail to
transfer to slaves.
named[9178]: 27-Mar-2012 05:56:00.798 general: error: zone
127.
Did it reject the zone when you used a too-large serial number? If so then
that explains why digging against the master doesn't show an updated serial.
On Mar 26, 2012, at 11:53 AM, Carlos Ribas wrote:
> Hello,
>
> I was doing some tests with DNSSEC in that zone. I used one day of
> sign
Hello,
I was doing some tests with DNSSEC in that zone. I used one day of
signature lifetime, now it is expired. All this happen when I was trying to
regenerate the signature.
In fact, the problem is that my master did not see the serial change.
If I run dig using the master I still got
On Mar 26, 2012, at 11:30 AM, Carlos Ribas wrote:
> I accidentally changed the serial number to one bigger than 32 bits and now
> I'm trying to reset the serial number. Following the manual of Bind9 I tried
> to add 2147483647 (2ˆ31-1) to the number and reload the server, but my slave
> is not u
Hello all,
I accidentally changed the serial number to one bigger than 32 bits and now
I'm trying to reset the serial number. Following the manual of Bind9 I
tried to add 2147483647 (2ˆ31-1) to the number and reload the server, but
my slave is not updating to the new zone serial number.
Here is w
10 matches
Mail list logo