3 ms·
Are there any other known sites that don't work with 1.1.1.1 but work fine on other resolvers?
by ikeboy 8y ago
Are there any other known sites that don't work with 1.1.1.1 but work fine on other resolvers?
- eastdakota 8y agoTypically, if you experience that, it’s because DNSSEC fails. 1.1.1.1 enforces DNSSEC. As does 8.8.8.8 in most, but not all, cases. Many other DNS resolvers do not enforce DNSSEC. Archive.is (and its directly affiliated sites) are the only exception like this I am aware of. And, to be clear, as a policy the 1.1.1.1 DNS does not block any sites from resolution.
- wolfgang42 8y agoI (random HN user) happen to know of lancaster.ac.uk (there was a comment thread a while back where this was mentioned).
- judge2020 8y agoThis is a problem of the 1^4 resolver not implementing DNAME support (either not a priority, or just in the backlog): https://community.cloudflare.com/t/www-lancaster-ac-uk-not-resolving-servfail/32211/3?u=judge https://community.cloudflare.com/t/www-lancaster-ac-uk-not-r...
- Smylers 7y agoIn what way doesn't it work? This is with my ISP's DNS (using which I can visit https://www.lancaster.ac.uk/ https://www.lancaster.ac.uk/ in a browser): $ host -t a lancaster.ac.uk lancaster.ac.uk has address 148.88.65.80 and this is with Cloudflare's: $ host -t a lancaster.ac.uk 1.1.1.1 Using domain server: Name: 1.1.1.1 Address: 1.1.1.1#53 Aliases: lancaster.ac.uk has address 148.88.65.80 Looks the same to me.