4 ms·
Nothing to fix. We are responding with what archive.* sends to us. They choose to send us incorrect data. See: https://news.ycombinator.com/item?id=19828702 ht
by jgrahamc 3y ago
Nothing to fix. We are responding with what archive.* sends to us. They choose to send us incorrect data.
See: https://news.ycombinator.com/item?id=19828702 https://news.ycombinator.com/item?id=19828702
- dredmorbius 3y agoWhy 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.
- dredmorbius 3y agoAnd while we're at it: <https://news.ycombinator.com/item?id=37149094 https://news.ycombinator.com/item?id=37149094>
- jgrahamc 3y agoYou can always email me (jgc@) with details.
- dredmorbius 3y agoEmail sent, to jgc.org and cloudflare.com, hopefully one of those works.