Hacker News Reader

Comment by keeperofdakeys | Hacker News Reader

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.

View on HN

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.

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.

How big a business do you have to be to use "free" DNS servers, but not big enough to run your own resolver?

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.

Yep, don't configure your servers with Google's public DNS servers but use the ones your public cloud provides.

Google DNS also has issues resolving DNSSEC-enabled Cloudflare domains.

Interesting! Do you have any examples?

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).

Do we know yet if CloudFlare has similar rate limits?

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....

Reply on news.ycombinator.com