6 ms·

Be careful with that, Google DNS (as an example) will start ignoring your DNS requests if you go over the rate-limit. Not an issue for home users, but an issue

Be careful with that, Google DNS (as an example) will start ignoring your DNS requests if you go over the rate-limit. Not an issue for home users, but an issue for any sizeable business.

noonespecial 9y ago
I have run into this in the wild. Presented as a weird, intermittent, "hey the internet is out" at the office around the same time each afternoon.
sytse 9y ago
Yep, don't configure your servers with Google's public DNS servers but use the ones your public cloud provides.
r1ch 9y ago
Google DNS also has issues resolving DNSSEC-enabled Cloudflare domains.
- fanf2 9y ago
  Interesting! Do you have any examples?
  - r1ch 9y ago
    Hmm, it seems like they may have fixed it, I can't seem to reproduce the problem I had (it would randomly fail to resolve CAA records for DNSSEC enabled domains).
mjevans 9y ago
Doesn't this just mean that you should be running your own caching resolver so that requests for common things don't constantly hit the upstream server? For those same common sites it should also be better performance anyway.
vamin 9y ago
Do we know yet if CloudFlare has similar rate limits?
- keeperofdakeys 9y ago
  I'd be surprised if they didn't have some form of rate limiting. Here are some reasons Google DNS does it https://developers.google.com/speed/public-dns/docs/security#rate_limit https://developers.google.com/speed/public-dns/docs/security....
voltagex_ 9y ago
How big a business do you have to be to use "free" DNS servers, but not big enough to run your own resolver?
- stubish 9y ago
  Probably the same way they use Lets Encrypt instead of purchasing certificates. Lots of free things actually are free, despite the negative training otherwise we get from some companies.