Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)

Re:Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.... by sintaxi on Saturday May 04, 2019 @07:15PM (#19829979)

Its preventing the DNS authority to know the IP of who is making the request.

CloudFlare decided its DNS should be the authority to the end user and Archive.is's DNS should be the authority only to CloudFlare. CloudFlare is breaking the bond between the end user and the Service provider.

What CloudFlare is doing is centralizing authority to itself rather allowing authority to be distributed to all owners of the domains as intended. An argument can be made that by using 1.1.1.1 you are granting CF permission to act in this role - some users may even prefer it.

[ Parent | on HN ]

Re:Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.... by slenk on Saturday May 04, 2019 @07:41PM (#19830114)

This is no different than any 3rd party DNS service. If the resolving DNS server you hit doesn't have a cached response, it reaches out to the upstream resolver. It doesn't pass your IP along to the upstream resolver

[ Parent | on HN ]

Re:Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.... by sintaxi on Sunday May 05, 2019 @01:28AM (#19831331)

Did I say something that was untruthful?

[ Parent | on HN ]

Re:Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.... by Operyl on Sunday May 05, 2019 @03:41AM (#19831669)

Perhaps not untruthful, but bending words to make it look malicious when it wasn’t? In general, your statement was just malicious to the point of “untrustworthy”.

[ Parent | on HN ]