Use a dedicated DNS-service on your local network which has the local IPs in it's DB. Use that DNS-service as your first/primary DNS on your local network (settings).
this post was submitted on 15 Jun 2023
6 points (100.0% liked)
Selfhosted
40173 readers
648 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:
-
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.
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 1 year ago
MODERATORS
Yes, this is called split horizon dns, basically, you have to control the DNS servers.
First, make a forwarding/resolver/cache, tell it to forward all requests for your_domain to your internal authoritative DNS server, it will return your internal IPs, externally though, when that domain is looked up, it will return the public ips of that host.
Very possible and done all the time.
At home you run a local DNS server, plenty of options out there especially as a self-hoster: bind, power dns, microsoft DNS if you're into windows. you can also combine this with something like pihole to block ads and junk at the dns level.
You create the dns zone on your dns server, internal devices use that dns server. You create the same zone on a public DNS provider like cloudflare or whoever (or host your own if you feel like it, on your vps), with public IPs.
Any of your devices coming/going from your home should be using DHCP to obtain an IP. At home your DHCP settings would hand out the local DNS server, anywhere else you go you'll be using other DNS servers that will resolve the public IP. It should all be pretty seamless and transparent once set up.
Depending on your wifi/router you could add a static DNS record for your domain while on the hi home network. The cached DNS will only matter while connected to the home wifi network. While on 5g you'll pick up the public DNS record. If it does some how cache the local DNS while public then shorten the ttl in the local DNS record
Not exactly the solution you're describing but Tailscale or ZeroTier could be the solution to your problem.
They're P2P VPNs which don't require static IPs or even open ports.
I set up Tailscale to forward my home subnet via my NAS. That allows transparent access of the NAS itself and any other device on the home network no matter where I am (as long as there's internet).
for PCs you can just add a hosts file entry, but that's probably not possible/too much work on phones. split horizon DNS is what you want.
This is the perfect opportunity to set up a pihole. Its primary purpose is to block ads network wide but since it is essentially a DNS with a block list you can also set custom dns-entries.