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

default DNS Resolver #7

Open
jol64 opened this issue Jun 27, 2023 · 0 comments
Open

default DNS Resolver #7

jol64 opened this issue Jun 27, 2023 · 0 comments
Labels
v2 To be completed in v2

Comments

@jol64
Copy link

jol64 commented Jun 27, 2023

in my setup, ResolverFactory.GetResolver returned 6 DNS servers with the first three being defunct w.r.t. application use (in fact they do what is expected for Hyper-V internals). The internals of Resolver obviously do not cycle through the listed DNS servers until they succeed.

Unfortunately the default resolver is a static variable in static class DnsResolver and all other methods use the default or need the optional IPAddress dnsHost = null which limits one to exactly one DNS server. One server may work if you specify DNS servers like 1.1.1.1 which are highly available, but best practice is to support multiple DNS servers.

Imho it would be preferable to allow to pass a Resolver instead of a single host, or as Stephan suggested in #5, get rid of the static class.

@danielsen danielsen added the v2 To be completed in v2 label Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v2 To be completed in v2
Projects
None yet
Development

No branches or pull requests

2 participants