▲ 25 ▼ Tailscale MagicDNS issues since 1.84.1 mac? (lemmy.world) submitted 1 year ago by thirdBreakfast@lemmy.world to c/selfhosted@lemmy.world 4 comments fedilink hide all child comments 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 updates ansible script, or Uptime Kuma checks. If I switch to IP addresses it works fine.
[+] just_another_person@lemmy.world 0 points 1 year ago* (last edited 1 year ago) (2 children) [removed by mod] permalink fedilink source hideshow 2 child comments replies: [–] heals@discuss.tchncs.de 1 point 1 year ago* 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. permalink fedilink source parent [–] thirdBreakfast@lemmy.world [S] 1 point 1 year ago It is only resolving for devices in the Tailnet. Kuma is checking they are all up, and this Ansible playbook is checking they have all their updates. I wouldn't have thought that was an unusual arrangement - and it's worked perfectly for about a year till about three weeks ago. permalink fedilink source parent
[–] heals@discuss.tchncs.de 1 point 1 year ago* 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. permalink fedilink source parent
[–] thirdBreakfast@lemmy.world [S] 1 point 1 year ago It is only resolving for devices in the Tailnet. Kuma is checking they are all up, and this Ansible playbook is checking they have all their updates. I wouldn't have thought that was an unusual arrangement - and it's worked perfectly for about a year till about three weeks ago. permalink fedilink source parent