5 ms·
- Bind for internal DNS zone - Pi-hole on 2 Raspberry Pi 4s - Chrony stratum 1 NTP from GPS on a Pi, my OPNsense router redirects all NTP traffic to it. - Em
by karlshea 4y ago
- Bind for internal DNS zone
- Pi-hole on 2 Raspberry Pi 4s
- Chrony stratum 1 NTP from GPS on a Pi, my OPNsense router redirects all NTP traffic to it.
- Emby (like Plex)
- Sonarr/Radarr/Prowlarr/Transmission with VPN/SABnbzd for collecting lots of little boxes that fall off trucks.
- Calibre-web
- LibreNMS
- Omada/UniFi controllers
- Home Assistant
- Tailscale
Almost all Dockerized now but it didn’t used to be. One Ubuntu 22.04 server I built with most of it, and another TrueNAS box I also built for file sharing and secondary Bind server.
I have a feeling I’ll be running a lot more after reading the rest of the comments!
- coolspot 4y ago> Pi-hole on 2 Raspberry Pi 4s Is this for redundancy? How does this work?
- karlshea 4y agoYes. They both have the same initial configuration, and DHCP hands out both IPs. They both in turn talk to the two bind servers for recursive resolving. (I got extremely irritated at my ISP’s DNS years ago which is why I was running bind, but now I keep it running behind Pi-hole for an internal domain name I started using because having bind running made that easy)
- somat 4y agopi-hole is at it's heart a recursive dns server, so you run two of them and advertise both in your dhcp(or put them in manually if you roll staticly)
- mypastself 4y agoI thought I was too hoity-toity for it, but I ended up gradually dockerizing most of the applications on my home server. It’s just so convenient.
- karlshea 4y agoReally made doing Ubuntu upgrades or clean installs way less of a chore. Some of that software requires an insane collection of packages, like Mono for Emby. And there started to be conflicting version issues with Python/PHP for awhile too.