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
Currently, for Hurricane Electric (dns-he), one has to enter their account username/password to be able to update the dynamic DNS entries for the DNS-based DCV. HE offers dynamic DNS functionality using a separate API and key that does not require this. I would like to see either the existing dns-he provider updated to be able to use this, or a new provider (e.g. dns-he-ddns) added that can leverage this functionality.
For example, I can update my DNS using the following curl command:
The password is whatever was previously set using the 🔃 "Generate a DDNS key" button in the HE interface (so the initial entry would still have to be added manually), but importantly does not have to be tied to your account password.
Use cases
This would allow for more secure dynamic DNS updates for domain control validation, as the credentials stored would only be able to manipulate the TXT record for the given hostname, as opposed to granting full account access to all domains/hostnames under the account.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What type of request is this?
Enhancement to existing add-on
Existing add-on name
Let's Encrypt
Describe the add-on or add-on enhancement
Currently, for Hurricane Electric (
dns-he), one has to enter their account username/password to be able to update the dynamic DNS entries for the DNS-based DCV. HE offers dynamic DNS functionality using a separate API and key that does not require this. I would like to see either the existingdns-heprovider updated to be able to use this, or a new provider (e.g.dns-he-ddns) added that can leverage this functionality.For example, I can update my DNS using the following curl command:
The password is whatever was previously set using the
🔃"Generate a DDNS key" button in the HE interface (so the initial entry would still have to be added manually), but importantly does not have to be tied to your account password.Use cases
This would allow for more secure dynamic DNS updates for domain control validation, as the credentials stored would only be able to manipulate the TXT record for the given hostname, as opposed to granting full account access to all domains/hostnames under the account.
Upstream project
No response
Anything else?
No response
Beta Was this translation helpful? Give feedback.
All reactions