Hacker News Reader

Italian here, I was trying to access anna's archive today (and libgen as well) without success, is there any easy workaround?

View on HN

Point your DNS at 8.8.8.8 and 8.8.4.4 - that's Google's public DNS and it currently resolves Annas Archive.

Frequently these ISP level blocks also redirect the normal port 53 traffic to their own servers so these settings are meaningless. What does work is DNS-over-HTTPS which can be enabled quickly and easily in both Chrome and Firefox and will side-step this block even against adversarial ISPs.

I wonder if an ISP could just serve NXDOMAIN for the canary domain? [0]

[0] https://support.mozilla.org/en-US/kb/canary-domain-use-appli...

"Frequently these ISP level blocks also redirect the normal port 53 traffic to their own servers"

No ISP is going to do nonsense like that for something like copywrite related compliance unless lots of money is forthcoming. An ISP can NXDOMAIN on their own DNS servers at a minimal cost. Doing 53/udp fiddling for all customers means CAM or similar expensive resource usage.

If you do find that your DNS is being redirected as TrueDuality describes, then yes DoH is an option. However if this is an issue then you have far bigger problems than not being able to access Anna's Archive.

Did they ban .gs and .se, too?

Those seem to be working! Thanks!

Reply on news.ycombinator.com