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

Report bugs to HE DDNS DNS API #5238

Open
markkuleinio opened this issue Aug 4, 2024 · 4 comments
Open

Report bugs to HE DDNS DNS API #5238

markkuleinio opened this issue Aug 4, 2024 · 4 comments

Comments

@markkuleinio
Copy link

This is the place to report bugs in the Hurricane Electric DDNS DNS API.

If you experience a bug, please report it in this issue.

Thanks!

Copy link

github-actions bot commented Aug 4, 2024

Please upgrade to the latest code and try again first. Maybe it's already fixed. acme.sh --upgrade If it's still not working, please provide the log with --debug 2, otherwise, nobody can help you.

@Gorgonbert
Copy link

Hi,

I'm running into a weird behavior on pfsense. The script can't update the TXT entry on the Hurricane Electric DNS.
From the logs, it looks to me as if the script uses the URL "https://dns.he.net" and that seems to fail.

To confirm, I tried this:

curl "https://dns.he.net/nic/update" -d "hostname=_acme-challenge.rolis.dnsswitzerland.ch" -d "password=something" -d "txt=test"

This failed just like on pfsense. With the URL "https://dyn.dns.he.net/" however, it works:

curl "https://dyn.dns.he.net/nic/update" -d "hostname=_acme-challenge.rolis.dnsswitzerland.ch" -d "password=something" -d "txt=test"

Did something change on the he.net server side?

@markkuleinio
Copy link
Author

markkuleinio commented Oct 8, 2024

Did something change on the he.net server side?

Note that this issue is about the dynamic DNS = dyn.dns.he.net (= using the record-specific auth key).

There is a separate (older) plugin for the full HE DNS (= dns.he.net), requiring using the full HE DNS credentials.

@Gorgonbert
Copy link

Oh... 🫢 sorry...
Indeed, I mixed up the plugins.
Looking closer at your plugin, I think you are probably fixing the issue I encounter. ;-)
Thank you.

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

2 participants