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!
view the rest of the comments
Wait I don't understand how changing your CNAME to A records resolved your problem. Did your wife's computer simply not resolve the CNAME records?
So I have my vms behind an opnsense with DHCP, the opnsense also creates local DNS records like vm1.opnsense. The pihole has conditional forwarding for .opnsense to the firewall, so I can resolve the domain everywhere in LAN.
I had CNAME records in the pihole for my actual domain (e.g. lemmy.nocturnal.garden) pointing to vm1.opnsense so I take a shortcut from inside the LAN, avoiding going "outside" via the public IP.
Mint/resolved resolves the .opnsense domains when I directly look them up, but for a reason I didn't fully understand, it does not work with a CNAME entry pointing to that. So I have up on the CNAME approach and created A records for each service, directly pointing to the VM's IP.
I'm curious as why you decided to setup pihole when you already have opnsense. More so that your records are in pihole and not opnsense
I've had pihole years before the opnsense, but also opnsense is not the main router but just sits in front of my homelab. The wifi etc is a FritzBox, which also acts as WAN for opnsense.
That way, everything still in the house still works if my homelab/opnsense is down. Pihole is on a pi in the FritzBox LAN.
That sounds overly complicated, why not have it all on opnsense instead of 3 different devices?
Is your opnsense unstable? Otherwise regarding network availability you are just introducing unnecessary failure points the network.
The point of the opnsense is that I can tinker with it without risking our home wifi. It needs to stay up for my wife, for our mqtt devices/home assistant etc.
I don't introduce points of failure to our home network which is the critical part. If something in the opnsense misbehaves, it only impacts my lab stuff. The FritzBox + Pihole combination has proven pretty stable over years, even though I'm considering getting a second Pihole device for high availability.
Ah right, I thought you were doing it like this
Internet -> Fritzbox + Pihole -> Opnsense -> Home Network
It makes sense now :D
Yeah that would be a bit convoluted :D