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.
this post was submitted on 15 Jun 2023
3 points (100.0% liked)
Selfhosted
40246 readers
589 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
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
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).
There's some great advice here on how to accomplish this, but a note of caution: If you're doing this split DNS on a device that you expect to be able to walk out the door with and continue working properly.. Some apps will cache DNS lookups even beyond the configured TTL. Meaning that a running app that thinks your server has a particular IP might stop working as soon as you walk outside of WiFi range and that IP is no longer reachable. And it might stay not working for quite a while. Ask me how I know this. :D
I feel like I know the answer already but how do you know this?
Because I tried this exact scenario with the Home Assistant app. Local IP for my HA server's hostname configured on my home router, public IP for the hostname elsewhere. I walk out my front door with the HA android app running on my phone, boom, loses connectivity to the HA server as soon as I'm out of wifi range and never recovers.. The local IP is no longer reachable and the app isn't smart enough to look up the new one.