Tailscale MagicDNS issues since 1.84.1 mac?
-
Has anyone seen a drop in magic DNS performance in the last month?
I'm having this in situations where the DNS would be getting hammered - for example my
apt updatesansible script, or Uptime Kuma checks. If I switch to IP addresses it works fine. -
Has anyone seen a drop in magic DNS performance in the last month?
I'm having this in situations where the DNS would be getting hammered - for example my
apt updatesansible script, or Uptime Kuma checks. If I switch to IP addresses it works fine.You've got a serious misconfiguration and are being rate-limited by their resolvers.
MagicDNS should only be resolving for devices on the Tailnet, not things like apt or Kuma. See here.
A Restricted Nameserver should be resolving for only your Tailscale Devices, and Global Server for everything else. You should never have normal services on your machines reaching out on Tailscale to query DNS unless you want the behavior you're current seeing, which is unnecessary.
-
You've got a serious misconfiguration and are being rate-limited by their resolvers.
MagicDNS should only be resolving for devices on the Tailnet, not things like apt or Kuma. See here.
A Restricted Nameserver should be resolving for only your Tailscale Devices, and Global Server for everything else. You should never have normal services on your machines reaching out on Tailscale to query DNS unless you want the behavior you're current seeing, which is unnecessary.
wrote on last edited by [email protected]Where exactly do you get the rate limiting part from?
100.100.100.100 is provided by the Tailscale daemon on your local device and pretty much all resolving is done locally based on the DNS rules you have configured for your tailnet. MagicDNS will resolve your tailnet clients locally based on the network map, other lookups will be forwarded to your LAN or exit-node DNS / split DNS servers or to your configured global DNS servers if you have the override enabled in admin panel.
