We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The https://github.com/libdns libraries¹ provide a uniform interface for updating DNS records across providers.
We could use these to implement dyndns: take the public IPv4 address of uplink0 and set it as an A record in the configured provider(s).
Personally, I use cloudflare for DNS, and have a little program which does these updates.
① Not entirely sure how ready they are. They come with a disclaimer.
The text was updated successfully, but these errors were encountered:
cmd/dyndns: prototype for dynamic DNS daemon (#50)
ead58ad
Updates #46. Signed-off-by: Matt Layher <[email protected]>
Just switched from my custom dyndns updater to the built-in dyndns, and it seems to work well!
Calling this done. Follow-up improvements can be tracked in a separate issue.
If you’re curious: @mdlayher and I built this feature on our twitch streams. Find the recording at:
https://youtu.be/2UDLZiL8im4?t=6288 (@mdlayher’s stream, https://www.twitch.tv/mdlayher) https://youtu.be/JW8Cg6JDXSc?t=6290 (@stapelberg’s stream, https://www.twitch.tv/stapelberg)
Sorry, something went wrong.
dyndns: don’t crashloop when config does not exist
f1e4ee0
related to #46
No branches or pull requests
The https://github.com/libdns libraries¹ provide a uniform interface for updating DNS records across providers.
We could use these to implement dyndns: take the public IPv4 address of uplink0 and set it as an A record in the configured provider(s).
Personally, I use cloudflare for DNS, and have a little program which does these updates.
① Not entirely sure how ready they are. They come with a disclaimer.
The text was updated successfully, but these errors were encountered: