Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNS in Chrome #883

Closed
174n opened this issue Jan 12, 2022 · 6 comments
Closed

DNS in Chrome #883

174n opened this issue Jan 12, 2022 · 6 comments

Comments

@174n
Copy link

174n commented Jan 12, 2022

Chrome doesn't resolve DNS queries to the yggdrasil addresses while firefox does. I found one solution to this problem, you might consider adding this for everyone by default

Add a network route to 2001:4860:4860::8888. Doesn't have to actually be functional (could just drop requests to it). As long as Chrome can connect a UDP socket to the address, it will pass the heuristic checking IPv6-connectivity.

https://chromium.googlesource.com/chromium/src/+/refs/heads/main/net/dns/README.md

@Jan69
Copy link

Jan69 commented Jan 12, 2022

works just fine with chromium for me, how can you run yggdrasil WITHOUT having a route, anyway?

@174n
Copy link
Author

174n commented Jan 12, 2022

The ipv6 addresses are being resolved correctly, but if I add an ip as AAAA DNS record it won't resolve in chrome. The DNS server was only added to the yggdrasil interface. You can try some from here, they won't work in chrome https://yggdrasil-network.github.io/services.html#dns

@zhoreeq
Copy link
Contributor

zhoreeq commented Jan 14, 2022

In practice, Google only allows "normie" web for Chrome users. It's beyond repair.

The only working solution is to use FF rn, or you can try some fork like Brave.

@174n
Copy link
Author

174n commented Jan 14, 2022

In practice, Google only allows "normie" web for Chrome users. It's beyond repair.

The only working solution is to use FF rn, or you can try some fork like Brave.

Can't just 2001:4860:4860::8888 route be added? It can just drop requests to it (so long as chrome can connect a UDP socket to the address), but it would be enough for DNS to function. I can't imagine someone switching their browser just because of yggdrasil. And yggdrasil is so easy to install (especially on windows) so even "normies" can potentially use it. Yggdrasil is such a great technology, the community shouldn't cripple it just because they don't like some things "normies" use. Yggdrasil isn't focused on privacy anyway I think.

@ansuz
Copy link

ansuz commented Jun 12, 2022

I believe chrome/chromium/similar-browsers can be launched with --enable-ipv6. This is an old bug that was known in the early days of cjdns development.

Now that more networks support ipv6 natively I think fewer people are likely to affected by this (I am not).

@neilalexander
Copy link
Member

Closing as this is an environmental issue.

@neilalexander neilalexander closed this as not planned Won't fix, can't repro, duplicate, stale Oct 21, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants