Open andrejohansson opened 3 years ago
Well, if you're using software that's on version zero point one, it's probably the software, not you :)
Could you re-run your query with the DOG_DEBUG
environment variable set to a non-empty string? This is looking similar to issue #2.
Seems it has trouble getting a default nameserver. A workaround of dog google.com -n 1.1.1.1
solved the issue for me.
@ogham This bug occurs because of this LOC. First adapter not always what we need. In my case it was Hyper-V adaper.
I can confirm that dog google.com -n 1.1.1.1
helped for me too, and I have a lot of adapters so what @SerialSmile concludes is very likely.
Windows 10 Pro. same problem.
This seems to be resolved by 8238e217c74485e84b204b3819445bc8b44da732 on master. I can verify it is fixed now.
When it's come to release?
In the next release I want to include some way to set the adapter.
Thanks for the reports, all
How's v0.2.0 coming along now ?
I just installed it using scoop and I encountered this exact error
Hi, I tried to build from the current master branch and found that the issue does not seem to be solved.
Please see the following logs.
OS Name: Microsoft Windows 11 Pro
OS Version: 10.0.22000 N/A Build 22000
System Type: x64-based PC
I was hitting this issue after installing Tailscale which creates a new adapter in Windows. I was able to mitigate the issue by setting the InterfaceMetric to a higher value (I changed the metric from 5 to 100).
I used this PowerShell command (interface index 11 is the Tailscale interface)
Set-NetIPInterface -InterfaceIndex 11 -InterfaceMetric 100
Well, if you're using software that's on version zero point one, it's probably the software, not you :)
4 years later, its the same version and the same problem tho... cough
Can´t seem to get this to work, am I missing something obvious?
Dog
Dig
Version information