Selfhosted

60409 readers

472 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Tailscale MagicDNS issues since 1.84.1 mac? (lemmy.world)

submitted 1 year ago by thirdBreakfast@lemmy.world to c/selfhosted@lemmy.world

6 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.

you are viewing a single comment's thread
view the rest of the comments

[–] just_another_person@lemmy.world 2 points 1 year ago* (last edited 1 year 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.