-
Notifications
You must be signed in to change notification settings - Fork 447
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
Update example multiaddrs of boostrap nodes #772
Update example multiaddrs of boostrap nodes #772
Conversation
This points to 2 new bootstrap nodes, as we would like to decouple the datacenter (`ams-1`, `lon-1`) from the peer id. Also, this (currently) uses both an EU and US based servers, instead of bother being EU-based.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR @mburns
I tried the browser example with the new addresses, but they are all failing:
WebSocket connection to 'wss://bootstrap.libp2p.io/p2p/QmQCU2EcMqAqQPR2i9bChDtGNJchTbq5TbXJJ16u19uLTa' failed: Error in connection establishment: net::ERR_NAME_NOT_RESOLVED
Is this blocked by https://github.com/protocol/bifrost-infra/pull/827 ?
Hrm. Nope, the new addresses have been live and in production for several months. I've kicked one of the instances that seemed wedged:
Otherwsie, all connect for me. |
I am able to dial using go-ipfs, but not in JS. The address is not being resolved. I am getting on websockets:
@jacobheun any ideas? |
@mburns @vasco-santos these are bad addresses. It "works" in go-ipfs because it already knows good addresses for those peers due to @vasco-santos we need to implement multiformats/js-multiaddr#94 (comment). The bootstrap addresses should ideally just be:
@mburns In order for the dnsaddr's to work we also need the TXT records to contain the A temporary workaround would be to use the underlying subdomains:
This isn't great because we're still hardcoding the subdomain addresses but until we add @vasco-santos let's sync up to get the dnsaddr resolution support done so we're no longer blocked there. |
Do we have any example on how the TXT records will look like? |
You can use dig to see the existing multiaddrs, Or a curl from Cloudflare's service: |
Cool thanks! I was missing the |
thanks for connecting those dots, @jacobheun
=>
|
@mburns so one problematic thing we have to deal with for wss addresses is that we can't resolve the domain in the dnsaddr record, because we need it for SSL resolution.
So I think it will need to look like:
And we have to avoid resolving dns4/dns6 addresses on the JS side. |
Great. I've pushed those changes:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Merging this into #782 with the doh resolver
Adds the new `dnsaddr` multiaddrs for browser bootstrapping peers per libp2p/js-libp2p#772 and libp2p/js-libp2p#782
This updates the docs to point to new(er) bootstrap nodes. Infra would like to decouple how we announce bootstrap records so that the datacenter (
ams-1
,lon-1
) is not strictly tied to a peer id (QmSol...
).These new examples are using servers on different continents, instead of both being EU-based.