-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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 local server as dns provider #1620
Comments
Hello, you can use: |
The setup that I have in place currently, but looking to possibly replace with lego for the sake of using tools that automate this task, is built on the principle of having an NS record for every server's
This has several advantages, like every server being entirely self-sustainable in terms of DNS needing only the authoritative nameserver to respond to queries in a way that is predictable and easy to automate, it even works programmatically without any configuration required per service and it alleviates all necessity for credential management.
This leads me to my point in regards to the methods suggested here; httpreq doesn't work in my case at all because no service is actually running, while exec with its current interface would require significant boilerplate code to ensure that the service is stopped. The code provided in #1621 would solve my issue exactly, as the built-in server could then simply host the response for the DNS query on demand and shut down right after that, at least as far as I can see. |
Welcome
How do you use lego?
Binary
Link to the DNS provider
Link to the API documentation
Additional Notes
I use coredns as my dns server, it does not support rfc2136 (dyndns), but i can use forward request like:
So I suggest running a local dns server to serve wildcard dns requests.
The text was updated successfully, but these errors were encountered: