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

Add support for desec.io #1

Open
vRobM opened this issue Aug 16, 2022 · 1 comment
Open

Add support for desec.io #1

vRobM opened this issue Aug 16, 2022 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@vRobM
Copy link

vRobM commented Aug 16, 2022

Please add support for https://desec.io the modern DDNS service w/ IPv6 support

@YoRyan YoRyan self-assigned this Aug 16, 2022
@YoRyan YoRyan added the enhancement New feature or request label Aug 16, 2022
@YoRyan
Copy link
Owner

YoRyan commented Aug 25, 2022

deSEC uses the No-IP protocol, so by setting the endpoint to https://update.dedyn.io, you can technically get DsDDNS to work with that service.

But, here's the rub: If deSEC doesn't receive both the IPv4 and IPv6 addresses in the same update request, it will delete the A or AAAA record that corresponds to the address that wasn't received in that request. DsDDNS doesn't currently support simultaneous updates like this; it requires A and AAAA records to be configured and updated separately, with two separate requests.

So my current thought is to keep the current configuration format, but allow DsDDNS to combine A/AAAA record pairs for the same hostname into single update operations. This would not only allow deSEC to be implemented, but also halve the number of requests for current Google Domains & No-IP users.

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

No branches or pull requests

2 participants