<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Bind 9.7 on CentOS 6.2<br>
<br>
<br>
Hi all,<br>
<br>
I am attempting to recreate a failure scenario of a slave server
that cannot contact its master for a zone. I am having a difficult
time following the log entries of what is occurring due to Bind not
seemingly following the SOA definitions for the zone. I have the
following set on this test zone:<br>
<br>
<tt>example.com IN SOA dns1.example.com.
root.dns1.example.com. (<br>
2012071914 ; serial<br>
60 ; refresh (1 minute)<br>
30 ; retry (30 seconds)<br>
120 ; expire (2 minutes)<br>
86400 ; minimum (1 day)<br>
)<br>
</tt><br>
<br>
<br>
I am running into the following issues:<br>
<ul>
<li>The refresh time seems to be ignored. Even though it is set at
60 seconds, it seemed to poll the master server somewhere
between 3 and 5 minutes. I had to define max and min refresh
time in /etc/named.conf to get it to respect this time. Is there
some internal limit to how low of a setting Bind will allow in
some of the SOA definitions? I was unable to find a minimum
limit for this when Googling <span class="moz-smiley-s1"><span>
:-) </span></span><br>
<br>
</li>
<li>I am seeing the following messages when it fails to contact
the master (as expected). Only problem is after it sends this
message I am not seeing an attempt to contact the master every
30 seconds as I am interpreting the "retry" limit to mean:</li>
<ul>
<li>zone example.com/IN: refresh: retry limit for master
10.32.69.1#53 exceeded (source 0.0.0.0#0)</li>
</ul>
</ul>
<p><br>
</p>
<p>Am I misunderstanding what Bind will log and attempt to do with
the "retry" limit? <br>
</p>
<p>Is there any documentation outlining what will actually occur,
and when, with a slave server when it cannot contact a zone's
master for updates?<br>
</p>
<p><br>
Thanks!<br>
</p>
</body>
</html>