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

IPv6 to IPv4 Fallback #686

Closed
MyIgel opened this issue Jan 31, 2018 · 3 comments
Closed

IPv6 to IPv4 Fallback #686

MyIgel opened this issue Jan 31, 2018 · 3 comments
Labels

Comments

@MyIgel
Copy link

MyIgel commented Jan 31, 2018

At the moment, if the domain resolves to an IPv4 and IPv6 address for a bridge, it client only tries the v6 address and ignores the v4 record.
It would be nice if the bridge could try to connect to the host via IPv4 if IPv6 fails for some reasons (port blocked or so).
The "Socket error on client [connection], disconnecting." is not really helpful while debugging that problem ;)

@karlp
Copy link
Contributor

karlp commented Jan 31, 2018

Surely this is a dns issue. If you are providing addresses in dns that you don't want to be using... stop providing them in dns. It's pretty unfeasible that every application in the world needs to try and implement their own policy of when and how to pick different dns results. That's the resolver's job!

@toast-uz
Copy link
Contributor

toast-uz commented Mar 3, 2018

@MyIgel is this a duplicate of #574 ?

@toast-uz
Copy link
Contributor

toast-uz commented Apr 7, 2018

Closing as duplicated of #574 .

@toast-uz toast-uz closed this as completed Apr 7, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Aug 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants