-
Notifications
You must be signed in to change notification settings - Fork 381
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
DNS TTLs are too low #1023
Comments
Agreed. |
What actions are to be taken to implement this? Are there any existing entries that have low TTLs? |
there's a whole bunch that have a ttl of 1 (the README encourages it, in fact). I'm still waiting on discussion of what out ttl should be though |
This was referenced Feb 16, 2024
Merged
#1149 retroactively updates TLS for all to |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Setting a default TTL of 1 second does not allow for proper caching and can put strain on the DNS network. The "best practice" is between 12 and 24 hours, but if that's too long it might make sense to follow Cloudflare, which sets their "Auto" TTL to 300 seconds (or 5 minutes)1.
In general, it's good practice to have a slightly longer TTL to enable faster queries2 and better redundancy.
The text was updated successfully, but these errors were encountered: