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.

all 5 comments

sorted by: hot top controversial new old
[–] 3 points 1 year ago (1 child)

I went and edited my hosts file and added all of my devices, but I only have a handful. Tailscale on macOS has a lot of bugs, this being one of many.

  • source
  • hideshow 1 child comment
  • [–] 3 points 1 year ago

    Hate that you’re downvoted for this. Tailscale is incredible software but it is buggy as hell.

    I gave up on 90% of the fancy features and just do most my routing from one node with good ol’ nftables and ip route/ip -6 route.

  • source
  • parent
  • [+] 0 points 1 year ago* (last edited 1 year ago) (2 children)
  • [–] 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.

  • source
  • parent
  • [–] [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.

  • source
  • parent