-
Notifications
You must be signed in to change notification settings - Fork 0
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
Possible to use Private DNS Zones? #1
Comments
Hi @devopsleigh! It's definitely tricky because Let's Encrypt servers require you to have the domain publicly available for you to get a publicly signed TLS certificate. This means that you need to actually own the domain and have public DNS records for it. However, there's a couple of solutions I can think that might work. I haven't tested these. Create both public and private DNS zones for the same domainIn this setup, the az-acme2keyvault function app would use a public DNS zone to coordinate certificate validation with the public Let's Encrypt servers. You could then use the private DNS zone (for the same domain) to serve all the other DNS records. No code changes would be needed for az-acme2keyvault. This allows you to get signed TLS certificates from Let's Encrypt while exposing only the validation TXT records publicly. However, it does mean you're limited to creating private DNS zones for domains you own. Set up your own ACME serverIn this setup, you'd have your own ACME server that signs certificates for your private DNS zone domains. This allows you to use any domain for the private DNS zone and you don't need a public DNS zone. However, there's a lot of things to consider first:
|
Brilliant! I'll try out option 1 today. I appreciate your detailed reply. |
I'd like to use Private DNS Zones with this solution. Will that work with a minor code change?
The text was updated successfully, but these errors were encountered: