I can’t imagine not using a proper internal DNS with split anymore.
I’m a big fan of Pihole (currently running it on a DietPi VM).
Being able to manage DHCP and DNS in a single place makes for much better control than the crappy DHCP from consumer routers. And almost any real DNS/DHCP server combo is better than those things.
Just rebuilt my PiHole over the last couple days, and it’s currently blocking 45% of DNS requests with no ill effects on any system - it’s a lot of Android app nonsense and a smart TV.
I’ve lost the Samsung TV on the TV, but I never used it anyway, and the TV is so much more responsive now.
Yea, smart TV… Bad news. It’s next on the list to get a Kodi box on it.
JasonDJ@lemmy.zip 1 week ago
This is one of the right answers, and probably the easiest.
But…who is your domain registered with? A lot of the big registrars (I.e. CF) can easily integrate into several opnsense plugins…namely ACME/HAProxy, and Dynamic DNS.
Dynamic DNS would make sure that “pubip.mydomain.com”, from the outside, always pointed to your Internet connection, even if your IP changes.
Then just register CNAMEs for your external services to point to your pubip.mydomain.com.
HAProxy reads the CNAME and directs it to the right service.
You can either use split DNS and have HAProxy listen on both the internal and external, and map DNS around that way…or you can just listen on your external interface and connect that way and only update one end.
Imo this is the more comprehensive solution, because this also easily solves certificates (via ACME). The last leg (from HAProxy to backend) and be unencrypted or just use long-life self-signed certs if you really care…but I wouldn’t worry about certs on the inside of a homelab.