this post was submitted on 15 Jun 2025
24 points (100.0% liked)

Selfhosted

48304 readers
901 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 day ago (1 children)

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.

[–] [email protected] 2 points 1 day ago* (last edited 1 day 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 dig or nslookup, 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.