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

feat(resolve): allow configurable dnsServers #341

Closed
wants to merge 2 commits into from

Conversation

SgtPooki
Copy link

This change allows users to call ma.resolve() with a dnsServers option that
will allow them to override the dnsServers used when resolving /dnsaddr/xxx multiaddrs.

Copy link
Author

@SgtPooki SgtPooki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

self review

Comment on lines +98 to +99
* In the browser, this is passed to dns-over-http-resolver, so the servers should be a DoH compatible url such as https://cloudflare-dns.com/dns-query
* In Node.js, this is passed to dns.resolve, so the servers should be an IP address or hostname (with optional port) such as '9.9.9.9'
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* In the browser, this is passed to dns-over-http-resolver, so the servers should be a DoH compatible url such as https://cloudflare-dns.com/dns-query
* In Node.js, this is passed to dns.resolve, so the servers should be an IP address or hostname (with optional port) such as '9.9.9.9'
* In the browser, this is passed to [dns-over-http-resolver](https://github.com/vasco-santos/dns-over-http-resolver#setserversservers), so the servers should be a DoH compatible url such as https://cloudflare-dns.com/dns-query
* In Node.js, this is passed to [dns.setServers](https://nodejs.org/api/dns.html#dnspromisessetserversservers), so the servers should be an IP address or hostname (with optional port) such as '9.9.9.9'

@achingbrain
Copy link
Member

Closing in favour of #373 as it allows specifying multiple DNS resolution strategies.

@achingbrain achingbrain deleted the feat/allow-configuring-dns-servers branch March 11, 2024 14:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants