Hacker News Reader

Comment by mNovak | Hacker News Reader

Archive link:

https://archive.ph/20260720174223/https://asia.nikkei.com/bu...

I'm in the US and I'm either getting NXDOMAIN or NOERROR (with no A record answer) back from every big nameserver I try (my ISP, Google, Cloudflare, etc.).

But a dig +trace archive.ph (which recurses all the way to the root locally) resolves it fine.

Is there some US-mandated DNS filtering I don't know about?

Hmm, does DoH work?

A pretty reasonable question. I guess it could be my ISP filtering.

Or rather could have been, since the issue seems like it was transient. I'm now getting resolutions.

Very strange, I wish I'd recorded what was going on better while it was broken.

You could try using archive.today to see where it would redirect you (some other archive TLDs are less filtered depending on ISP, and I believe .today autoselects the best one for your IP).

No, the archive.today (and .ph, .is, etc.) operator configured their nameservers to return invalid responses to Cloudflare's 1.1.1.1 resolvers because Cloudflare doesn't forward EDNS client subnet info (for the privacy of their users). The operator claims to need this information for load-balancing but I don't buy that argument.

As far as I was aware, their issue was resolved, but sometimes I still see failures so I don't really know.

Also, "US-mandated DNS filtering" would be a violation of the 1A except in narrow circumstances (which don't exist here) so I'm not sure that that should be your first thought...

Reply on news.ycombinator.com