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

Disable DNS resolution when using TLS #400

Closed
acogoluegnes opened this issue Aug 24, 2018 · 0 comments
Closed

Disable DNS resolution when using TLS #400

acogoluegnes opened this issue Aug 24, 2018 · 0 comments
Assignees
Milestone

Comments

@acogoluegnes
Copy link
Contributor

The client performs by default a DNS resolution when only one server address is provided. This is to enable DNS-based load-balancing, see #138. As stated in #138 (comment) it makes TLS hostname verification fail, because the hostname of the server certificate isn't likely to match the IP resolved by the DNS query.

For 4.x and 5.x, the client shouldn't use DNS resolution as soon as TLS is enabled. This would at least avoid making TLS troubleshooting even more difficult.

DNS resolution would then need to be explicitly set up as of 6.0.0.

References #138, #394.

@acogoluegnes acogoluegnes added this to the 4.8.0 milestone Aug 24, 2018
@acogoluegnes acogoluegnes self-assigned this Aug 24, 2018
acogoluegnes added a commit that referenced this issue Aug 27, 2018
Fixes #400

(cherry picked from commit 8dde8b5)
acogoluegnes added a commit that referenced this issue Aug 27, 2018
acogoluegnes added a commit that referenced this issue Aug 27, 2018
References #400

(cherry picked from commit 02164d7)

Conflicts:
	src/test/java/com/rabbitmq/client/test/ConnectionFactoryTest.java
acogoluegnes added a commit that referenced this issue Aug 27, 2018
acogoluegnes added a commit that referenced this issue Aug 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant