News for hackers. Stuff that matters.

A comment on Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1). Parent comment

Re:Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.... by icebraining on Saturday May 04, 2019 @08:57PM (#19830420)
I don't see what they can do, short of sending fake DNS replies with their own webserver IPs, which is worse for the integrity of DNS.
[ Parent | on HN ]
Re:Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.... by SimeVidas on Sunday May 05, 2019 @10:58AM (#19833116)
Shouldn’t there be some kind of standard DNS response for this? There are dozens of different HTTP status codes for all kinds of scenarios. Doesn’t DNS have something like that? I know almost nothing about DNS, I’m just curious.
[ Parent | on HN ]
Re:Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.... by icebraining on Sunday May 05, 2019 @11:21AM (#19833229)
The thing is, the server sends a real response, it's just not the same response as it sends to other recursive resolvers.

Imagine it's HTTP, and the site sent a 404 to your proxy, but you knew it generally sent a 200 to other proxies, what should you do? Send the 404, or override it with your own status code? Cloudflare is saying they are not OK with overriding codes.

[ Parent | on HN ]