Comment on Tailscale MagicDNS issues since 1.84.1 mac?
thirdBreakfast@lemmy.world 1 week agoIt 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.
just_another_person@lemmy.world 1 week ago
It’s not only resolving for devices in the Tailnet if you saw apt hitting MagicDNS resolvers though. You have something misconfigured.
If you’re not familiar with networking or how DNS resolvers work, I’d start by checking your current node connected to the Tailnet and determine where your DNS requests are coming from with
digornslookup, then check your local resolver configurations, and other devices as well. Make absolutely sure that you’ve got a split DNS config (meaning you’re not using the fqdn of nodes in the Tailnet and not shortnames, and that the custom domain is showing as a target for searching on restricted resolvers in your resolver configs. Then branch out and check your other nodes to make sure they have a similar configuration.