servfail only for a zone

John Miller johnmill at
Mon Jul 13 17:33:01 UTC 2015

Something I'm noticing is that your SOA record fields are quite small:    3600    IN    SOA 2015070601 1200 180 3600 3600

Specifically, your expiration time (first of the 3600s) is set to one
hour.  This means that if ns2 hasn't contacted ns1 in an hour, the zone
will be invalid on ns2.  If you're making a whole ton of updates, then the
small times make sense, but for the zone you posted, that doesn't seem to
be the case.  Normally it's not a problem, but if you can't respond to a
communication outage between the two nameservers within an hour, the second
will stop working.

This is just a guess, but network communication/failed zone transfer seems
the most likely culprit for something like this (entire zone returns

John Miller
Systems Engineer
Brandeis University
johnmill at

On Mon, Jul 13, 2015 at 1:19 PM, Lucio Crusca <lucio at> wrote:

> And here is the zonefile at the master ns1:
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the bind-users mailing list