Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dynamic DNS RFC 2136 Support #4

Open
tynes opened this issue May 3, 2019 · 0 comments
Open

Dynamic DNS RFC 2136 Support #4

tynes opened this issue May 3, 2019 · 0 comments

Comments

@tynes
Copy link
Contributor

tynes commented May 3, 2019

I'd like to be able to dynamically update my zone file in a safe and secure way. Looking for prior art, I came across this RFC for Dynamic DNS - https://tools.ietf.org/html/rfc2136

Looking through the bns codebase, I didn't see any mentions of Dynamic DNS or ways to update the zone file dynamically without building a wrapper around the AuthServer and calling setFile with an updated zone file. This doesn't seem like the ideal solution.

RFC 2136 at least uses the DNS protocol itself to update the zone file, so that an additional HTTP server doesn't need to be ran. It also includes a permission system

the requestor's permission to update the RRs named in
the Update Section may be tested in an implementation dependent
fashion or using mechanisms specified in a subsequent Secure DNS
Update protocol. If the requestor does not have permission to
perform these updates, the server may write a warning message in its
operations log, and may either signal REFUSED to the requestor, or
ignore the permission problem and proceed with the update.

Supporting a very easy way for users to update their zone files is important for Handshake.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant