6 comments

1
DNS issues with archive.is are due to archive fucking with DNS requests. It's not a fault of Cloudflare/Google/etc because they are receiving poisoned answers from archive.
1
Then why are those the only 2 DNS providers not working with archive.is?
1
Because they do not forward client IP to archive, archive cannot serve their site from geo location that matches the client so archive poisons the answer instead.
1
> Because they do not forward client IP to archive This is malicious config on the part of the DNS providers then. They have no problem forwarding client IP to countless other domains, but for some reason Archive is an exception? Fuck them, then.
1
It's not "malicious config", it is intentional to protect client privacy. I don't think they forward client IP to anyone at all - it is just archive that is butthurt and spoils the answers. The only exception here seems to be Archive but I agree with the sentiment. Fuck them.
1
I can tell you for fact they forward IP to any of my sites just fine, not to mention countless client sites that I know for a fact receive 'Remote_Addr' and similar headers when testing them using those DNS.