Closed UpperCenter closed 2 years ago
Hi there - so Stubby Manager is a bit dumb when it comes to trying to set localhost for the interfaces... Under the hood it blindly tries to set up for all 'physical' interfaces via a Powershell script StubbySetDns.ps1
which is installed on your machine in C:\Program Files (x86)\Stubby
(so you can try running it manually if you like or even hacking it):
https://github.com/Sinodun/Stubby_Manager/blob/develop/os/windows/StubbySetDns.ps1
Stubby then double checks the state of all active networks and I think the problem is it treats the VMware adapter as an active network for this check, but the underlying interface probably doesn't get set to Localhost by the above script because it is not physical?
I suspect if you do a Connection Test it might work because you Ethernet/Wifi connections are using localhost? You can take a look in the Logs tab to see what connections Stubby is actually making. We need to add some intelligence to the UI to select which specific interfaces Stubby should control otherwise it can end up in this inconsistent state on some devices....
Thanks for the info, it does seem to work just fine even if it does just stay on "updating"
Hi All,
Apologies if this is a simple issue, but I'm unable to get Stubby to connect to any DNS servers. Application logs are:
My system is set to use
localhost
as the DNS server, so I'm unsure why the service is failing here.So far I've tried reinstalling the application, and reseting my network settings.
Running Windows 11 Pro