Skip to content

Add Netlify DNS to the list of DNS Providers for the DNS Challenge #2496

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

Open
rasulkireev opened this issue Dec 21, 2022 · 4 comments
Open

Comments

@rasulkireev
Copy link

Hello all,

I'm trying to enable SSL for domains created via Netlify DNS. I've ran into a problem where Netlify DNS is setting up an SSL Certificate for all subdomains I create there, and there is no way to disable it there.

I asked for the solution on their channel and got this. Their recommendation is to use a DNS challenge. Unfortunately, NGINX Proxy Manager doesn't yet support Netlify DNS for that.

Can anyone help me with this?

I'm a Backend Engineer with about 3 years of experience and would love to help adding this feature, but am currently in the dark. If someone who knows more about this could provide help, feedback, that would be awesome! Thanks a ton in advance.

@AridTag
Copy link

AridTag commented Dec 22, 2022

You can try using the CI build from #2402 or use the changes from that branch to create your own docker image (as I have until it gets merged, if it gets merged). You just select DNS Multi from the dropdown and fill in the details for your specifc DNS provider.

See the Usage section here: https://pypi.org/project/certbot-dns-multi/

Copy link

github-actions bot commented Feb 1, 2024

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions github-actions bot added the stale label Feb 1, 2024
@DanielRios549
Copy link

I have this problem. I added a subdomain my own Netlify domain, but it throws an error to generate the certificate, the log says: no valid A records found for sub.domain.com; no valid AAAA records found for sub.domain.com". That's really true, I have a CNAME entry only, but I don't know if it throws this error because it really doesn't exist or if it simply cannot reach it.

@github-actions github-actions bot removed the stale label Jul 31, 2024
Copy link

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions github-actions bot added the stale label Mar 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants