Skip to content
New issue

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

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

Already on GitHub? # to your account

Add unresolved inital router address to list of resolved initial roter addresses #565

Closed
wants to merge 1 commit into from

Conversation

jjaderberg
Copy link
Contributor

In scenarios with SNI, connecting to resolved addresses does not work.
The driver consistently fails to retrieve a routing table using the initialRouter because the address is explicitly resolved before making connection(s). It succeeds to get a routing table only because the same initial address is also put into the table as a router.

By adding the initial router address unresolved to the list of addresses to try, the driver should be able to work both with SNI and with multi-record DNS bootstrap addresses.

…er addresses

In scenarios with SNI, connecting to resolved addresses does not work.
To retain the multi-record DNS capability for bootstrap address,
add the unresolved address after the resolved addresses.

Co-Authored-By: Tobias Johansson <tobias.johansson@neotechnology.com>
@jjaderberg jjaderberg added the bug label Feb 21, 2019
@jjaderberg jjaderberg changed the base branch from 2.0 to 1.7 February 21, 2019 15:23
@zhenlineo
Copy link
Contributor

zhenlineo commented Feb 27, 2019

@jjaderberg Could you give a try of the fix proposed by #566

@zhenlineo zhenlineo closed this Feb 27, 2019
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants