You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 24, 2022. It is now read-only.
I'm opening this issue more as an FYI for someone else who might be experiencing the same issue.
DNSAgent seems to be broken by something in the Windows 10 v1903 update and beyond. The service will start (or it can be run interactively) and the log stream will show requests coming in, but they don't seem to get forwarded on to the upstream DNS servers. I'm not sure if this is specific to my setup, but I've experienced the same issue on two different systems now.
I've moved to CoreDNS now as a replacement, using NSSM to run it as a Windows service.
The text was updated successfully, but these errors were encountered:
Follow up to the above - I think this issue might be related to the Internet Connection Sharing service which also spins up a DNS service of some kind, and seems to get enabled by default for some reason.
Looks like this might be causing a conflict when binding to the port perhaps. I've not fully tested this though!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm opening this issue more as an FYI for someone else who might be experiencing the same issue.
DNSAgent seems to be broken by something in the Windows 10 v1903 update and beyond. The service will start (or it can be run interactively) and the log stream will show requests coming in, but they don't seem to get forwarded on to the upstream DNS servers. I'm not sure if this is specific to my setup, but I've experienced the same issue on two different systems now.
I've moved to CoreDNS now as a replacement, using NSSM to run it as a Windows service.
The text was updated successfully, but these errors were encountered: