ungoogled-chromium: Secure DNS fails on .works domain
When Secure DNS is turned on and set to use anything other than OS default, .works domain cannot be resolved and returns ERR_NAME_NOT_RESOLVED.
Example: https://howhttps.works/
I’m not sure if this issue is specific to UG, but I cannot reproduce it on Chrome.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 20 (17 by maintainers)
It might have nothing to do with
.works. I could resolve19216811.worksfor example, maybe the fact that the domain containshttpsis the problem?IPv4-only host:
IPv6+IPv4 host:
The last one is actually trying to resolve AAAA, but fails:
So it might indeed be trying to resolve IPv6 through DoH and fails to connect.
Calling DoH with
dns-query?name=howhttps.works&type=aI get IPv4; calling withdns-query?name=howhttps.works&type=aaaaI predictably get nothing.BTW: Compare that to any other IPv4-only domain. They all have something even for
aaaa, but nothowhttps.works, so it might be the domain that is bugged.BTW BTW: Google says: “DNSSEC validation failure.” and “Invalid denial of existence of howhttps.works/aaaa”. https://dns.google/resolve?name=howhttps.works&type=aaaa
I can reproduce this. It only seems to be an issue for howhttps.works, other .works addresses function normally like the one @rany2 mentioned.
Even weirder, if you visit howhttps.works once without secure DNS enabled then the site will work fine afterwards once it’s re-enabled. This works on other pages on the domain and with a hard refresh so it isn’t just a cached version of the page.
Can reproduce it on Linux:
So I figured out what’s going on. An IPv6 check is being performed (I guess due to the site having an IPv6 address available?) and
add-ipv6-probing-option.patchis forcing a true value unless--enable-features=SetIpv6ProbeFalse/chrome://flags/#set-ipv6-probe-falseis set. Enabling that flag allows the site to function normally for me.I think it’ll be a good idea to update that patch to return the actual result rather than always assuming true. Then the flag could just override that value. Alternatively we could default to false since it does that already for those on wifi: https://source.chromium.org/chromium/chromium/src/+/refs/tags/127.0.6533.72:net/dns/host_resolver_manager.cc;l=1423-1430
I assume that @alienbob has IPv6 connectivity and that those of us encountering the issue don’t?
Edit: Looks like I had that backwards then
Nope. As I said (but perhaps not explicitly enough) , I had never even heard of the site, and turned on Secure DNS before accessing that URL for the first time.
Same for me.
Thank you, right as I was about to install a VM 😀