Various users related problem with 188.8.131.52 and providers and routers, correct? Was 184.108.40.206 a good idea? Or is best an new alternative of numbers to your resolvers? Example: 220.127.116.11 and 18.104.22.168.
We think 22.214.171.124 was an awesome idea. We knew in advance that the entire address space had been highly abused and enjoy solving tough problems. Response from network providers and ISPs has generally been nothing short of fabulous (at least the portions of the conversations to which I have been privy) and occasionally colourful.
126.96.36.199 is already available as a Cloudflare resolver along with 2 IPv6 addresses.
I like dns service of Cloudflare and now use how my primary and secondary dns. It is my favorite dns service now. I only waiting correction of problem of latency here.
“188.8.131.52 is already available as a Cloudflare resolver along with 2 IPv6 addresses.”
Why not add 184.108.40.206 how alternative to 220.127.116.11 with problems? It is an suggestion only. I like of dns service of Clouflare.
I believe that there’s so much redundancy in Cloudflare’s network that a secondary DNS entry is (mostly) unnecessary. I’m sure there’s some edge case similar to the current situation where it’s nice to fall back to a secondary.
I can’t ever recall seeing any DNS query of mine falling back to 18.104.22.168, but it feels good to have a backup.