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

DNS-based Discovery: DNS Resolver #615

Closed
jm-clius opened this issue Jun 14, 2021 · 2 comments · Fixed by #709
Closed

DNS-based Discovery: DNS Resolver #615

jm-clius opened this issue Jun 14, 2021 · 2 comments · Fixed by #709
Assignees

Comments

@jm-clius
Copy link
Contributor

Subtask of #452
Created as partial fulfilment of #552

Problem

vacp2p/rfc#385 proposes a method to discover a bootstrap list of Waku v2 peers via DNS. This list is encoded in TXT records, stored in a domain. A DNS Resolver component must be created that can look up TXT records from a given subdomain.

NOTE: Since this component is easy to stub, it can be developed last.

@Menduist
Copy link
Contributor

Hey, just stumbled into this issue.
FIY, we also have to resolve TXT dns as part of the dnsaddr resolving in libp2p, so for vacp2p/nim-libp2p#580 we added the dnsclient library, and integrated it in chronos.

Once this is merged (currently finishing up), you will be able to just do:
let record = await switch.nameResolver.resolveTxt("status.im") (or something like that)

We also plan to integrate other resolvers in the future (eg, Dns-Over-Https), which you could also benefit from using our resolver :)

@jm-clius
Copy link
Contributor Author

Oh, dope! Thanks a lot, @Menduist. This will make my task significantly easier :)

@jm-clius jm-clius moved this from In Progress to Backlog in Deprecated: nwaku Aug 16, 2021
@jm-clius jm-clius moved this from Backlog to In Progress in Deprecated: nwaku Aug 24, 2021
Deprecated: nwaku automation moved this from In Progress to Done Aug 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

Successfully merging a pull request may close this issue.

2 participants