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

Netlify DNS #595

Closed
Luit opened this issue Jul 14, 2018 · 10 comments · Fixed by #1144
Closed

Netlify DNS #595

Luit opened this issue Jul 14, 2018 · 10 comments · Fixed by #1144

Comments

@Luit
Copy link

Luit commented Jul 14, 2018

I was wondering, with Netlify not having a documented API, would it be acceptable to still implement a DNSProvider using the API utilized by app.netlify.com? I'm currently using bash + curl + jq to have exec be my DNSProvider for Traefik, but it would be nicer to have Traefik (lego) handle this internally.

I'd happily implement something to put up as a pull request. Thoughts?

@ldez
Copy link
Member

ldez commented Jul 14, 2018

I am curious to see your bash script, could you share it with us?

@Luit
Copy link
Author

Luit commented Jul 14, 2018

I'll make it a little neater and gist it. Maybe tomorrow.

@Luit
Copy link
Author

Luit commented Jul 14, 2018

In a support chat with Netlify I've had a nice chat about the API, and it appears some work on the API is on its way. Not sure what exactly, but might get more info in a few days. Meanwhile I'll still re-build what I've done in bash using Go, to get a feel for what I'd like to do to build this DNSProvider.

@Luit
Copy link
Author

Luit commented Jul 23, 2018

My current script: https://gist.github.com/Luit/5c7e2c31718f84ec709c7a21838adbe8

I had some trouble requesting a certificate for wildcard AND apex domain using Træfik. Looks like the DNS request for the first validation puts the _acme-challenge TXT record in Let's Encrypt's DNS cache and the next validation still sees that first record, instead of the new one. Added a sleep $TTL to the cleanup because of that. Because of this, cleanup takes 2 minutes.

@AnderssonPeter

This comment has been minimized.

@ldez
Copy link
Member

ldez commented Mar 5, 2020

@Luit do you have some news from Netlify?

@ldez
Copy link
Member

ldez commented Mar 5, 2020

@Luit
Copy link
Author

Luit commented Mar 5, 2020

@Luit do you have some news from Netlify?

I kind of forgot about it thanks to the aforementioned script.

@oscartbeaumont
Copy link

oscartbeaumont commented Apr 27, 2020

You could checkout netlify-managed-dns which I created. It has a library which could potentially be used to add this feature until the Managed DNS API is added to the official client, which doesn't seem to be happening anytime soon if the slow response is to go by. I would also be wiling to make changes to my API package if needed.
Correction: Looks like netlify/open-api#211 is making some progress finally which is awesome!

@ldez
Copy link
Member

ldez commented Apr 27, 2020

Netlify seems to react on the official client:
netlify/open-api#211 (comment)

We will wait a bit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

4 participants