4 ms·
You really should use a local caching resolver, even if you set your upstream to google's resolvers. Just install pdns-recursor and you're good to go.
by baudehlo 13y ago
You really should use a local caching resolver, even if you set your upstream to google's resolvers.
Just install pdns-recursor and you're good to go.
- klaruz 13y agoYes, and google will throttle you if you make too many requests.
- ars_technician 13y agoIf nginx caches for 300s and that's the only reason you are installing pdns-recursor, that's unnecessary technical debt in your production pipeline.
- nodesocket 13y agoAgree, won't DNS do this caching automatically with valid=300s?
- sneak 13y agoI believe that nginx will do the caching with valid=300s. "DNS" does not let the client set the record TTL, and "DNS" in this case would be a round-trip request to the Google DNS servers listed in the config snippet - precisely what it was suggested be avoided.
- midas007 13y agoOn large deployments, every bastion (internet-facing host that handles traffic) should gets its own caching resolver and a copy of the internet-facing zones, pushed by puppet/chef. Helps a bunch w/ DDoS if the shop is too custom for CloudFlare || similar.