-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
Only works when I explicitly set @8.8.8.8
?
#144
Comments
Can you paste the exact contents of |
👋🏻 Sure thing...
|
Same problem on my side, it does not work any more without manually specifying the DNS server with a $ doggo www.github.com --debug @192.168.78.31
time=2024-08-06T15:49:37.545+02:00 level=DEBUG msg="LoadNameservers: Initial nameservers" nameservers=[192.168.78.31]
time=2024-08-06T15:49:37.545+02:00 level=DEBUG msg="Added nameserver" nameserver="{Address:192.168.78.31:53 Type:udp}"
time=2024-08-06T15:49:37.545+02:00 level=DEBUG msg="LoadNameservers: Final nameservers" nameservers="[{Address:192.168.78.31:53 Type:udp}]"
time=2024-08-06T15:49:37.545+02:00 level=DEBUG msg="initiating UDP resolver"
time=2024-08-06T15:49:37.545+02:00 level=DEBUG msg="Attempting to resolve" domain=www.github.com. ndots=0 nameserver=192.168.78.31:53
NAME TYPE CLASS TTL ADDRESS NAMESERVER
www.github.com. CNAME IN 3187s github.com. 192.168.78.31:53
github.com. A IN 37s 140.82.121.4 192.168.78.31:53
$ doggo www.github.com --debug
time=2024-08-06T15:49:44.339+02:00 level=DEBUG msg="LoadNameservers: Initial nameservers" nameservers=[]
time=2024-08-06T15:49:44.339+02:00 level=DEBUG msg="No user specified nameservers, falling back to system nameservers"
time=2024-08-06T15:49:44.339+02:00 level=DEBUG msg="Loaded system nameservers" nameservers="[{Address:192.168.78.31:53 Type:udp} {Address:192.168.78.1:53 Type:udp} {Address:10.42.0.1:53 Type:udp}]"
time=2024-08-06T15:49:44.339+02:00 level=DEBUG msg="initiating UDP resolver"
time=2024-08-06T15:49:44.339+02:00 level=DEBUG msg="initiating UDP resolver"
time=2024-08-06T15:49:44.339+02:00 level=DEBUG msg="initiating UDP resolver"
time=2024-08-06T15:49:44.339+02:00 level=DEBUG msg="Attempting to resolve" domain=www.github.com. ndots=0 nameserver=192.168.78.31:53
time=2024-08-06T15:49:44.339+02:00 level=DEBUG msg="Attempting to resolve" domain=www.github.com. ndots=0 nameserver=10.42.0.1:53
time=2024-08-06T15:49:44.339+02:00 level=DEBUG msg="Attempting to resolve" domain=www.github.com. ndots=0 nameserver=192.168.78.1:53
time=2024-08-06T15:49:49.341+02:00 level=ERROR msg="Error looking up DNS records" error="context deadline exceeded" The 3 servers are in my |
This error reminds me of fastly/cli#289 |
I hava same problem! |
Observed the same problem but only on my Macbook. Same install on Linux workstation works fine so it appears to be isolated to MacOS. A little further investigation, the issue goes away when I stand up my Wireguard VPN. After addtional research, it appears there is an invalid DNS server being handed out by my local ISP. That solves the issue of why the VPN tunnel worked as it provided new DNS servers to use. The trace appears to correctly query the second DNS server in my configuration (8.8.8.8) but still fails to resolve. Even after adding a 10s timeout increase it will not resolve.
|
👋🏻
I've just brew installed the latest release (1.0.4) and I tried the following query, which times out:
I tried all sorts of different hostnames and they all timeout.
I then checked the debug flag...
OK, interesting. No initial nameservers, but looks like the system nameservers should suffice, but nope, it still times out.
I then try explicitly setting
@8.8.8.8
and it works...What's strange is that if I don't specify 8.8.8.8 then it'll switch to system nameservers, and the first one in the list it tries is...
...which is the same one it uses when I explicitly set 8.8.8.8 (which is when it works 🤦🏻 )
I'm not sure what I'm doing wrong here as I have a colleague who is using the same Homebrew installed version and it works fine right out of the box 🤔
The text was updated successfully, but these errors were encountered: