zlacker

[return to "Tell HN: Archive.is inaccessible via Cloudflare DNS (1.1.1.1)"]
◧
1. regner+r1[view] [source] 2019-05-04 18:50:01
>>ikeboy+(OP)
Cloudflare returns a proper response for me.

  nslookup archive.is 1.1.1.1
  Server:  1.1.1.1
  Address: 1.1.1.1#53

  Non-authoritative answer:
  Name: archive.is
  Address: 134.119.220.26
◧◩
2. V99+X5[view] [source] 2019-05-04 19:30:02
>>regner+r1
It's possible your ISP is intercepting all traffic for port 53 and sending it to their own nameservers (which do send client subset) instead of you actually taking to cloudflare's 1.1.1.1 at all.
◧◩◪
3. abtinf+O8[view] [source] 2019-05-04 19:52:03
>>V99+X5
Links for documented instances of this practice?
◧◩◪◨
4. V99+4b[view] [source] 2019-05-04 20:09:46
>>abtinf+O8
I don't know of any particular popular concrete instance, but why is it hard to believe? It's trivial to implement and would be brought to you by the same people who think serving ads for NXDOMAIN is a good idea.

https://www.dnsleaktest.com/what-is-transparent-dns-proxy.ht...

[go to top]