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

Resolve hostnames using netty's DNS resolver #498

Closed
mp911de opened this issue Apr 1, 2017 · 0 comments
Closed

Resolve hostnames using netty's DNS resolver #498

mp911de opened this issue Apr 1, 2017 · 0 comments
Labels
type: feature A new feature
Milestone

Comments

@mp911de
Copy link
Collaborator

mp911de commented Apr 1, 2017

Netty 4.1 allows using unresolved socket addresses so netty can perform non-blocking DNS resolution. ClientResources should default to netty DNS resolution (via DnsResolver) if netty 4.1 is in use.

@mp911de mp911de added the type: feature A new feature label Apr 1, 2017
@mp911de mp911de added this to the Lettuce 4.4.0 milestone Apr 1, 2017
@mp911de mp911de changed the title Investigate on netty DNS resolver use Resolve hostnames using netty's DNS resolver Apr 1, 2017
mp911de added a commit that referenced this issue Apr 1, 2017
Lettuce now defaults to netty's DNS resolution upon connect when using netty 4.1. DnsResolver returns an empty array of addresses to signal an unresolved address. Netty performs a non-blocking DNS lookup.
mp911de added a commit that referenced this issue Apr 1, 2017
Lettuce now defaults to netty's DNS resolution upon connect when using netty 4.1. DnsResolver returns an empty array of addresses to signal an unresolved address. Netty performs a non-blocking DNS lookup.
@mp911de mp911de closed this as completed Apr 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature A new feature
Projects
None yet
Development

No branches or pull requests

1 participant