1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced?

Re:1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced? by ocdtrekkie on Friday March 30, 2018 @12:23PM (#16717444)

I wonder if, given that we now have a number of reasonably decent DNS services, if we can make software better to obscure/divide up our DNS use.

Take your 1.1.1.1, 8.8.8.8, 9.9.9.9, maybe your ISP DNS, etc., check against them randomly to try and avoid giving any one of them all of your DNS request traffic, maybe look up the same address on two of them to confirm that you're getting the same destination from both?

[ Parent | on HN ]

Re:1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced? by mtgx on Friday March 30, 2018 @03:14PM (#16718962)

I'm waiting for Facebook to get 6.6.6.6.

That's a DNS service everyone would love to use, right?

[ Parent | on HN ]

Re:1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced? by bsder on Friday March 30, 2018 @03:53PM (#16719282)

If you are Chinese, you would. 1, 6 and 8 are lucky numbers to Chinese.

I suspect that the whole reason why 8.8.8.8 is a Google DNS server is that they were originally only 4.4.4.4 until someone Chinese pointed out that 4 is an unlucky number. :)

[ Parent | on HN ]

Re:1.1.1.1 Cloudflare DNS Resolver Soon to Be Announced? by cm2187 on Friday March 30, 2018 @12:32PM (#16717525)

Well for me it is really useful to renew let’s encrypt certificates. When doing DNS validation, you must enter a TXT entry as a response to a challenge. Having multiple public DNS is useful to ensure the entries have propagated before letting letsencrypt know they can query them. OVH’s Anycast DNS servers propagation for instance is really non deterministic. It may have propagated when queried from one location but not yet from another.

[ Parent | on HN ]