-
Notifications
You must be signed in to change notification settings - Fork 1.8k
MagicDNS lookups have 5s delay on macOS #5308
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
Comments
Can you paste the output of |
It's quite long - I uploaded the output as a text file: edit: adding the output in an expandable section so you don't to download a file I uploaded:
DNS configuration
resolver #1 resolver #2 resolver #3 resolver #4 resolver #5 resolver #6 resolver #7 resolver #8 resolver #9 resolver #10 resolver #11 resolver #12 resolver #13 resolver #14 resolver #15 resolver #16 resolver #17 resolver #18 resolver #19 resolver #20 resolver #21 resolver #22 resolver #23 resolver #24 resolver #25 resolver #26 resolver #27 resolver #28 resolver #29 resolver #30 resolver #31 resolver #32 resolver #33 resolver #34 resolver #35 resolver #36 resolver #37 resolver #38 resolver #39 resolver #40 resolver #41 resolver #42 resolver #43 resolver #44 resolver #45 resolver #46 resolver #47 resolver #48 resolver #49 resolver #50 resolver #51 resolver #52 resolver #53 resolver #54 resolver #55 resolver #56 resolver #57 resolver #58 resolver #59 resolver #60 resolver #61 resolver #62 resolver #63 resolver #64 resolver #65 resolver #66 resolver #67 resolver #68 resolver #69 resolver #70 resolver #71 resolver #72 resolver #73 resolver #74 resolver #75 resolver #76 DNS configuration (for scoped queries) resolver #1 resolver #2 |
I was able to reproduce this issue by configuring split DNS with
Now that I have reproduced this issue, I'll be able to debug it locally and I'll post an update by the end of the week. |
I'm running into this or something very similar here. Tested on 1.36 and now that I've upgraded on 1.38.3. In my case with Tailscale DNS enabled, any attempt to resolve an entry in Resolving host on my local network shows a delay but not massive:
Resolving entry in
This effects pretty much everything except ping: curl, browser, nc, etc. Switching Having to turn off Tailscale DNS to do anything local kinda sucks.
|
Also having this issue, potentially related to golang/go#49253 ? |
I hit this issue just now as well. The DNS lookup takes 5s on a mac, but works fine if i include the "dnsname.ts.net" at the end, also works fine on linux machine on the same network. $ cat curl_format.txt
time_namelookup: %{time_namelookup}
time_connect: %{time_connect}
time_appconnect: %{time_appconnect}
time_pretransfer: %{time_pretransfer}
time_redirect: %{time_redirect}
time_starttransfer: %{time_starttransfer}
———
time_total: %{time_total}
#slow on mac
$ curl -w "@curl_format.txt" -o /dev/null -s ts-homelab:2019/config
time_namelookup: 5.004892time_connect: 5.018599time_appconnect: 0.000000time_pretransfer: 5.018672time_redirect: 0.000000time_starttransfer: 5.033309———time_total: 5.033499%
#fast will full TS domain name
$ curl -w "@curl_format.txt" -o /dev/null -s ts-homelab.<magic-dnsname>.ts.net:2019/config
time_namelookup: 0.002773time_connect: 0.017509time_appconnect: 0.000000time_pretransfer: 0.017545time_redirect: 0.000000time_starttransfer: 0.031057———time_total: 0.031281
#linux machine
$ curl -w "@curl_format.txt" -o /dev/null -s ts-homelab:2019/config
time_namelookup: 0.001284time_connect: 0.011801time_appconnect: 0.000000time_pretransfer: 0.011831time_redirect: 0.000000time_starttransfer: 0.021655———time_total: 0.021723 |
Ok |
What is the issue?
MagicDNS lookups from my macOS client have a consistent 5 second delay when using only the machine name, but lookups are fast as expected when using the full name with *.{domain}.beta.tailscale.net.
Steps to reproduce
Lookup with machine name only:
If I lookup by the fqdn rather than machine name, resolution is quick:
This delay is noticeable via browser, curl, nc, etc. when using only the machine name. Interestingly, using ping resolves quickly - I'm not sure if there is some caching going behind the scenes there.
example with nc:
Are there any recent changes that introduced the issue?
n/a
OS
macOS
OS version
12.4
Tailscale version
1.28
Bug report
BUG-b190cd840a3a272d8a2b36a4311dbd6aa24e76f2d13cd3cffe3127e0e7100cab-20220805193117Z-891f6b9c55e18126
The text was updated successfully, but these errors were encountered: