-
Notifications
You must be signed in to change notification settings - Fork 233
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
nxdomain responses include huge timeouts #342
Comments
I believe that the last field in the SOA record should be set to a much lower value (eg, |
Good point, 60sec should be sufficient. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There doesn't appear to be a way to set minTTL for nxdomain replies at this time. This would be very helpful to prevent upstream dns servers from breaking how acme-dns works. I'm running into this issue currently with an infoblox based dhcp/dns server upstream. It holds onto the nxdomain reply for an hour+ and never checks back with acme-dns till it's too late and the letsencrypt request has expired.
The text was updated successfully, but these errors were encountered: