They had some "interesting" DNS records

dns.google

(Quote)

I used to use Google DNS, then switched to CloudFlare, then CloudFlare started heavily rate limiting the OVH network so I switched back to Google. I use Q9 in some stuff.

Quad9, Layer3/CenturyLink, or my own DNS servers.

dnscrypt-proxy using these

All pretty quick (anycast), support ANY, no dns hijacking, and probably not farming my personal data.

But IMO worse is when your first one (or two) servers are dead, and glibc gets stuck at every DNS query.

which causes DNS traffic to triple with the intention to intentionally discard 2/3 of all responses?

Documentation https://dns.pl/formularze/NASK_EPP_Extension_en.pdf

Also be noted that glibc try each server in sequence and try the next only after one times out while musl queries them all in parallel.

Across Google's, CF's, NTT's, or running my own, I have never ran into a situation where I'd say "gosh, this DNS is so slow! I wish it would be just a bit faster!" We're long past th

If your datacenter provides DNS, then you should either use that or create your own resolvers. The response time will always be faster.

First DNS is datacenter, second DNS local VM server, then Google, then CF last. I recommend putting your local ISP DNS before CF/Google.

Datacenters DNS usually plus 8.8.8.8 + 1.1.1.1 or opendns too.

I am using 1.1.1.1 1.0.0.1 cloudflare what bout you?

(Quote)

(Quote)

And yeah their support is absolutely useless. I spent a couple weeks talking to support trying to verify that they don't charge for DNS zones. At the end they had an engineer inform me that they in fa

I'm using MXroute with Cloudflare, so no visible hosting server IP addresses though mail DNS record.