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

Support for deSEC.io #822

Open
rosieeyes opened this issue May 16, 2021 · 6 comments
Open

Support for deSEC.io #822

rosieeyes opened this issue May 16, 2021 · 6 comments

Comments

@rosieeyes
Copy link

deSEC.io is a free, open-source DNS host. I've been using it for the past couple of days, seems to work pretty well thus far. The API reference is documented here.

I'm happy to work on a PR for this myself. Anything else I should know before cracking on with the developer guide?

@rosieeyes
Copy link
Author

rosieeyes commented May 31, 2021

After some reading further into deSEC's API, I think it might be best to develop support an API tool for deSEC.io separately from lexicon. This is mainly as it wouldn't be possible to do a bunch of zone and account management actions, as well as creating some (admittedly obscure) RRsets, via lexicon.

If no-one disagrees, I would recommend closing this issue.

@rosieeyes
Copy link
Author

In fact, deSEC.io should be compatible with the PowerDNS provider already in lexicon. It's worth someone testing it to make sure of that though.

@TBJ
Copy link

TBJ commented Jul 16, 2022

In fact, deSEC.io should be compatible with the PowerDNS provider already in lexicon. It's worth someone testing it to make sure of that though.

I couldn't get it to work. It seems like the structure of deSEC's API URL:
https://desec.io/api/v1/domains/{name}/rrsets/
is different than that of regular powerDNS:
http://{domain}/servers/localhost/zones/{name}

Shame too, as deSEC is free, allows for subdomain zones, and also supports DNSSEC.

@peterthomassen
Copy link

I think it might be best to develop support an API tool for deSEC.io separately from lexicon. This is mainly as it wouldn't be possible to do a bunch of zone and account management actions, as well as creating some (admittedly obscure) RRsets

Can you provide some details on that? Perhaps we can improve things on the deSEC side. (I'm from the team.)

@renne
Copy link
Contributor

renne commented Jan 31, 2023

@peterthomassen
Currently we're using desec.io for the rerverse DNS zones of our Yunohost instance and Cloudflare for the forward zones.
It's quite annoying to have forward and reverse zones at different providers with different web-interfaces/APIs.
With desec.io support in Yunohost/lexicon I would happily move the forward zones from Cloudflare to desec.io.

@renne
Copy link
Contributor

renne commented Jun 28, 2023

push ...

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

4 participants