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

Jump to bottom

DNS Lookup - Custom resolver is not used #390

Closed
BornToBeRoot opened this issue Dec 13, 2020 · 0 comments · Fixed by #395
Closed

DNS Lookup - Custom resolver is not used #390

BornToBeRoot opened this issue Dec 13, 2020 · 0 comments · Fixed by #395
Labels
🐛 bug

Comments

@BornToBeRoot
Copy link
Owner

Describe your issue: Resolver cannot be changed. It's always the Windows DNS server...

Steps to reproduce the issue:

  1. Change the resolver
  2. Try to resolve a host

NETworkManager version: 2020.12.0

Windows version: 10

.NET-Framework version: SDK 5.0
@BornToBeRoot BornToBeRoot changed the title DNS Lookup - Resolver cannot be changed DNS Lookup - Custom resolver is not used Dec 13, 2020
BornToBeRoot added a commit that referenced this issue Dec 13, 2020
@BornToBeRoot
Close #390
e11aab9
@BornToBeRoot BornToBeRoot mentioned this issue Dec 13, 2020
Merged
BornToBeRoot added a commit that referenced this issue Dec 14, 2020
@BornToBeRoot
Fix #390 - Use custom dns resolver (#395)
3cd8d39 
* NetworkInterfaceType 53 added - Close #375

* Close #390

* Code improved, documentation added

Co-authored-by: BornToBeRoot <BornToBeRoot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
🐛 bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix #390 - Use custom dns resolver BornToBeRoot/NETworkManager
1 participant
@BornToBeRoot