@chazwhiz yes you can. Setup a subnet and just tell Tailscale to use your dns. I’m guessing you already have your dns pointing to NPM?
Selfhosted
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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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!
Can you be more specific?
Look at subnets below. App Connectors might also work for what you're trying to accomplish.
Tailscale has a NextDNS integration, so I use that to point my made-up internal domain to the Tailscale ip of my NAS. Works well with subdomains. When I’m on my local network (and not connected to Tailscale), my pihole directs the same url to the local ip.
To clarify, when you’re external or on the tailnet, you want the Tailscale ip. On the local network, you want the local ip.
Acronyms, initialisms, abbreviations, contractions, and other phrases which expand to something larger, that I've seen in this thread:
| Fewer Letters | More Letters |
|---|---|
| DNS | Domain Name Service/System |
| IP | Internet Protocol |
| NAS | Network-Attached Storage |
3 acronyms in this thread; the most compressed thread commented on today has 5 acronyms.
[Thread #1016 for this comm, first seen 23rd Jan 2026, 23:55] [FAQ] [Full list] [Contact] [Source code]
I'm not an expert, take this with a very big grain of salt.
But I think what you want here is for your home server tailscale to act as an exit node for your remote connection.
This will mean that your phone for example will route traffic through your home server, using its AdGuard DNS.
You can even set it up to conditionally use it as an exit mode, iirc.
Interesting. I saw the exit node feature but didn’t look into it closely. I’ll check it out. Thanks!
Also use advertise-routes to get access to the network as opposed to just the node. Like e.g.
--advertise-routes=192.168.1.0/24
Yes, also Tailscale already provides hostname dns for every device on your tailscale net.
I know it gives me their magicdns, like server.wackyname.ts.net, I'm talking about using my own domain.
slap the tailscale ips into your dns entries then. I do that.
Same. Works great
By default Tailscale devices prefer the local DNS server for any hostname that’s not part of your Tailscale network, unless you’ve configured a global DNS server. There’s also the option to configure split DNS and have a different DNS server for certain domains (for example your own domain). You can also add search domains to allow short hostnames to be resolved to FQDNs of your choice.
Do a DNS rewrite at AGH, but instead of the LAN IP make it the Tailscale IP of your NPM machine. Then configure AGH's IP address as one of the global nameservers on your Tailscale admin panel
Delete all A/AAAA records on Cloudflare, only use it for registrar purposes and the occassional certs authentication.
Do a DNS rewrite at AGH, but instead of the LAN IP make it the Tailscale IP of your NPM machine
Wouldn't that prevent any devices that don't have tailscale from using it even locally?
Yes.
If you want to access your NPM stuff on both Tailscale and LAN, either:
- Advertise a subnet route for your LAN range, configure Tailscale devices to use it, and use your LAN IP on the AGH rewrite, or
- Split Horizon: Have your DNS respond with a Tailnet IP when it's queried from the Tailnet range, and respond with a LAN IP when queried from LAN. AGH cannot do this, but other software like Technitium can