Hacker News new | ask | show | jobs
by jgrahamc 1035 days 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

2 comments

You can always email me (jgc@) with details.
Email sent, to jgc.org and cloudflare.com, hopefully one of those works.
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.