@lbutlr wrote:
>
> If I remove "update-policy local; " the nsupdate works, but it seems
> like it should have worked with the update-policy since I was in fact
> local to the bind server.
The "local" keyword enables server-side support for `nsupdate -l`, which
makes dynamic updates really easy to
On 20 May 2019, at 20:45, @lbutlr wrote:
>
> On 20 May 2019, at 16:21, Noel Butler wrote:
>> allow-update { key "keyname"; };
>
> Ah, no I did not. The instructions I found, as I mentioned in a later post,
> were to add grant dons-key. iOS this a change in 9.14, because I did not have
>
On 20 May 2019, at 16:21, Noel Butler wrote:
>allow-update { key "keyname"; };
Ah, no I did not. The instructions I found, as I mentioned in a later post,
were to add grant dons-key. iOS this a change in 9.14, because I did not have
to do this in 9.12?
> and nsLOOKUP ?
Just a thinko.
did you allow for it under the zone ? Adding a key as such will not give
you global operations
zone foo {
...
allow-update { key "keyname"; };
...
}
and nsLOOKUP ? Its either to early in the morning here and i'm
mis-reading what you're doing, or you should be us
On 19 May 2019, at 18:27, @lbutlr wrote:
> This is the same key block that is in named.conf. I am launching NSLOOKUP
> with -k admin.key, but when I try to make a change and then "send", I get
> "update failed: REFUSED."
I found a page that recommended adding a ddns-key and then adding "grant
The most obvious thing is to look at the zone and see if that key is
included in an allow-update statement for the zone.
Bob
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
bind-users mailing list
bind-u
6 matches
Mail list logo
