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.

Sign up for GitHub

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

Jump to bottom

p2p: support dns entrypoints #3156

Closed
dshulyak opened this issue Mar 29, 2022 · 0 comments
Closed

p2p: support dns entrypoints #3156

dshulyak opened this issue Mar 29, 2022 · 0 comments
Assignees
@abergasov
Labels
good first issue

Comments

@dshulyak
Copy link
Contributor

Libp2p accepts DNS entrypoint for the node. Example:

/dns4/bootstrap-0.mainnet.filops.net/tcp/1347/p2p/12D3KooWCVe8MmsEMes2FzgTpt9fXtmCY7wrq91GRiaC8PHSCCBj

In the existing deployment scheme we create several nodes and then connect every other node to them. It makes deployment more complex, and more importantly, relies on IP addresses being the same all the time.

Instead, in the new deployment scheme, we will generate entrypoints in advance and share them for every node in the cluster.
@dshulyak dshulyak mentioned this issue Mar 29, 2022
Closed
@abergasov abergasov mentioned this issue Apr 18, 2022
Closed
7 tasks
@abergasov abergasov linked a pull request Apr 18, 2022 that will close this issue
support dns addresses #3178
Closed
7 tasks
@abergasov abergasov mentioned this issue Apr 19, 2022
Closed
4 tasks
bors bot pushed a commit that referenced this issue Apr 28, 2022
@abergasov @evt
support dns addresses (#3180)
35d14a0 
## Motivation
Now for bootnodes can be used links with dns addresses.
DNS resolve address on connect
Closes #3156

## Changes
<!-- Please describe in detail the changes made -->

## Test Plan
<!-- Please specify how these changes were tested 
(e.g. unit tests, manual testing, etc.) -->

## DevOps Notes
<!-- Please uncheck these items as applicable to make DevOps aware of changes that may affect releases -->
- [x] This PR does not require configuration changes (e.g., environment variables, GitHub secrets, VM resources)
- [x] This PR does not affect public APIs
- [x] This PR does not rely on a new version of external services (PoET, elasticsearch, etc.)
- [x] This PR does not make changes to log messages (which monitoring infrastructure may rely on)


Co-authored-by: Eugene Toropov <[email protected]>
@dshulyak dshulyak closed this as completed May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@abergasov abergasov

Labels
good first issue
Projects
None yet
Milestone
No milestone
2 participants
@dshulyak @abergasov