Ask HN: Archive.is Captcha Problems Lately?

>>mattta+(OP)
Check your DNS, there are issues using Cloudflare to reach archive.{is | li | today | etc }

Google DNS and others work where Cloudflare does not.

Using Cloudflare (1.1.1.1) vs. Google (8.8.8.8) I get different IP resolution:

  for u in archive.ph archive.is archive.li archive.vn archive.fo archive.md;
  do
      echo ">>> ${u} <<<";
      host -t A $u 1.1.1.1;
      host -t A $u 8.8.8.8;
  done

Results:

  >>> archive.ph <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.ph has address 192.210.214.166
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.ph has address 23.137.248.133
  >>> archive.is <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.is has address 198.23.187.186
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.is has address 23.137.248.133
  >>> archive.li <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.li has address 192.210.214.166
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.li has address 23.137.248.133
  >>> archive.vn <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.vn has address 192.210.214.166
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.vn has address 23.137.248.133
  >>> archive.fo <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.fo has address 192.210.214.166
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.fo has address 23.137.248.133
  >>> archive.md <<<
  Using domain server:
  Name: 1.1.1.1
  Address: 1.1.1.1#53
  Aliases: 
  
  archive.md has address 192.210.214.166
  Using domain server:
  Name: 8.8.8.8
  Address: 8.8.8.8#53
  Aliases: 
  
  archive.md has address 23.137.248.133

Cloudflare: Fix your shit.

>>dredmo+sFi
Nothing to fix. We are responding with what archive.* sends to us. They choose to send us incorrect data.

See: >>19828702

>>jgraha+vIi
Why and/or how is Archive Today managing to send Cloudflare different responses than other DNS providers?

I'd suggest you kick your "integrity of DNS" principle in the interest of "rough consensus, working code". And yes, you can do that without passing on user-specific EDNS to AT, who're quite likely to obtain just that information through the subsequent HTTP GET request in any event.

zlacker