<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFCC" text="#000000">
Just be sure that WHEN your master dies, the slaves will stay
authoritative for long enough that you can get the master up without
working night shift.<br>
<br>
<div class="moz-cite-prefix">On 19/02/13 21:17, Dave Warren wrote:<br>
</div>
<blockquote cite="mid:5123DDCB.9060701@hireahit.com" type="cite">On
2/18/2013 23:20, Matus UHLAR - fantomas wrote:
<br>
<blockquote type="cite">On 19.02.13 10:25, Noel Butler wrote:
<br>
<blockquote type="cite">One thing I need to point out, your SOA
timings seem extreme...
<br>
<br>
refresh 86400 drop that to 3h
<br>
retry 3600, drop to 900
<br>
</blockquote>
<br>
I don't see the reason for doing these, unless NOTIFY does not
work, but in
<br>
such case it's the NOTIFY that should be fixed...
<br>
</blockquote>
<br>
I agree in principle. However, the costs of having a low refresh
probably aren't that significant, whereas all it takes for a
NOTIFY to get missed is a packet or three getting dropped, and
having zones out of sync might be more significant.
<br>
<br>
Or, put another way, dropping REFRESH from 24 hours to 3 hours is
what, an additional 8 DNS queries per zone, per secondary, per
day? Unless your zones normally receive only a few hundred queries
a day, these numbers are so trivial that they probably don't
matter, whereas having your secondaries return out of date
responses is potentially more annoying.
<br>
<br>
Retry too seems like a good candidate to keep very low since it
only applies when there is a problem.
<br>
<br>
But in an ideal world, we've probably just spent more time talking
about it than will result in any savings from tweaking these
numbers.
<br>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
</pre>
</body>
</html>