-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Labels
Component: mosquitto-broker
Status: Duplicate
Type: Enhancement
A new feature for a minor or major release.
Comments
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
added
Status: Duplicate
Type: Enhancement
A new feature for a minor or major release.
Component: mosquitto-broker
labels
Mar 3, 2018
Closing as duplicated of #574 . |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
Component: mosquitto-broker
Status: Duplicate
Type: Enhancement
A new feature for a minor or major release.
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 ;)
The text was updated successfully, but these errors were encountered: