zlacker

[parent] [thread] 5 comments
1. dredmo+(OP)[view] [source] 2023-08-16 15:41:34
Interesting ...

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.
replies(1): >>jgraha+33
2. jgraha+33[view] [source] 2023-08-16 15:54:21
>>dredmo+(OP)
Nothing to fix. We are responding with what archive.* sends to us. They choose to send us incorrect data.

See: >>19828702

replies(2): >>dredmo+r6 >>dredmo+Z6
◧◩
3. dredmo+r6[view] [source] [discussion] 2023-08-16 16:07:23
>>jgraha+33
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.

◧◩
4. dredmo+Z6[view] [source] [discussion] 2023-08-16 16:09:55
>>jgraha+33
And while we're at it: <>>37149094 >
replies(1): >>jgraha+pl
◧◩◪
5. jgraha+pl[view] [source] [discussion] 2023-08-16 17:08:42
>>dredmo+Z6
You can always email me (jgc@) with details.
replies(1): >>dredmo+HP
◧◩◪◨
6. dredmo+HP[view] [source] [discussion] 2023-08-16 19:04:11
>>jgraha+pl
Email sent, to jgc.org and cloudflare.com, hopefully one of those works.
[go to top]