<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#ffffcc" text="#000000">
Thanks, it does not matter much, more for the understanding.<br>
<br>
I had forgotten about signing, without it might have been a
question.<br>
<br>
On 05/01/11 13:29, Phil Mayers wrote:
<blockquote cite="mid:4D246445.2030309@imperial.ac.uk" type="cite">On
01/05/2011 11:45 AM, Sten Carlsen wrote:
<br>
<blockquote type="cite"> Maybe just a detail without much
significance. Will the zone become
<br>
dynamic when you enable updates OR when you have actually done
the first
<br>
update - i.e. created the .jnl file?
<br>
</blockquote>
<br>
A dynamic zone is a zone that allows dynamic updates, so the
former. You don't need a .jnl file, and can remove it (provided
you have flushed the updates and don't need the IXFR history) and
it'll still be dynamic.
<br>
<br>
Another example, if you dnssec sign a zone, but leave it as
static, then later set:
<br>
<br>
auto-dnssec maintain;
<br>
<br>
...and
<br>
<br>
zone name {
<br>
allow-update { ... };
<br>
}
<br>
<br>
...the zone will start to be "looked at" for DNSSEC signature
maintenance as soon as you do an "rndc reconfig". It might take
minutes, hours or days before a re-signing occurs, but it's
dynamic immediately.
<br>
<br>
But I guess it's a matter of terminology.
<br>
_______________________________________________
<br>
bind-users mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:bind-users@lists.isc.org">bind-users@lists.isc.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://lists.isc.org/mailman/listinfo/bind-users">https://lists.isc.org/mailman/listinfo/bind-users</a>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
</pre>
</body>
</html>