Hi there! We're currently working on implementing Private Link and DNS integration at scale. I came across some guidance on this topic, and I'm wondering if there's a way to set the DNS record TTL to something other than the default 10 seconds. We're concerned that a short TTL may overload our DNS forwarders. Any insights would be appreciated!
3 Answers
The TTL is usually set for each individual record. You might want to automate this with a script to adjust all your records accordingly. Also, check this out for guidance: https://learn.microsoft.com/en-us/azure/dns/dns-operations-recordsets. Alternatively, you could create an Azure policy to enforce a specific TTL upon record registration, but be prepared for it to be a little complex with ARM templates.
If you're worried about performance issues with your DNS server, you might have bigger problems to tackle first. Just make sure you're fully optimizing other aspects of your setup too!
You can definitely adjust the TTL by changing the policy or creating a new one specifically to update your DNS records. That might help with the overload issue you mentioned.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures