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

Selfhosted

48262 readers
514 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] 0 points 1 day ago* (last edited 1 day ago) (3 children)

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.

[–] [email protected] 1 points 11 hours ago* (last edited 11 hours 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.

load more comments (2 replies)