You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I created a pull request #59 where it is possible to use ddnskeys to have restricted access to a subdomain as defined in the zone file with update-policy. The shared secret will be still the same for all domains but further checking is done by the bind9 server with the ddnskey. Therefor you have to make sure that the default ist to not have access without a ddnykey.
This method may break compatibility with existing systems since it adds a variable to the request. For the future it may be a good idea to remove the current "shared secret check" and replace it with ddnskeys in a way to keep compatibility. By using ddnskeys we can archive ACL by delegating the task to the bind9 server itself.
But there is not much support for it right now and to get it to work requires some manual adjustments.
Golit
added a commit
to Golit/docker-ddns
that referenced
this issue
Aug 31, 2020
The rest-api does not need to check the shared secret because bind itself
can check it. This change also allows to have different shared secrets for
different zones.
See dstapp#55
Please add the ability to specify a dedicated secret for a given subdomain.
E.g. via environment variable
The text was updated successfully, but these errors were encountered: