Thanks, it does not matter much, more for the understanding.
I had forgotten about signing, without it might have been a question.
On 05/01/11 13:29, Phil Mayers wrote:
> On 01/05/2011 11:45 AM, Sten Carlsen wrote:
>> Maybe just a detail without much significance. Will the zone become
>> dynami
On 01/05/2011 11:45 AM, Sten Carlsen wrote:
Maybe just a detail without much significance. Will the zone become
dynamic when you enable updates OR when you have actually done the first
update - i.e. created the .jnl file?
A dynamic zone is a zone that allows dynamic updates, so the former. Yo
Maybe just a detail without much significance. Will the zone become
dynamic when you enable updates OR when you have actually done the first
update - i.e. created the .jnl file?
On 05/01/11 10:15, Phil Mayers wrote:
> On 01/05/2011 03:01 AM, p...@mail.nsbeta.info wrote:
>>
>> Hello,
>>
>> When add
On 01/05/2011 03:01 AM, p...@mail.nsbeta.info wrote:
Hello,
When adding a statement of something like:
allow-update { 127.0.0.1; };
to the zone configuration, this zone will become a dynamic zone, is it?
Yes.
You can also do:
allow-update { key NAME; };
...and in newer versions of bind I
On 01/05/2011 03:32 AM, Paul Ooi Cong Jen wrote:
Hi,
Nope. Dynamic zone require keys exchange for zone transfer.
This is not correct.
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Hi,
Nope. Dynamic zone require keys exchange for zone transfer.
--
Paul Ooi
On 05-Jan-2011, at 11:01 AM, p...@mail.nsbeta.info wrote:
>
> Hello,
> When adding a statement of something like:
> allow-update { 127.0.0.1; };
> to the zone configuration, this zone will become a dynamic zone,
Hello,
When adding a statement of something like:
allow-update { 127.0.0.1; };
to the zone configuration, this zone will become a dynamic zone, is it?
Thanks.
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/li
7 matches
Mail list logo
