Doesn't work on Windows 10 ~v1903 onwards

[DevOpsFu]

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.

[DevOpsFu]

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!