

I didn’t read the article but based on the headline it sounds interesting. I’m just worried about adoption rate but I guess they’ve got to start somewhere
I didn’t read the article but based on the headline it sounds interesting. I’m just worried about adoption rate but I guess they’ve got to start somewhere
I’m not sure that’s possible on most routers but I’m very much not an expert in networking
I don’t think that’s how it works with my router. I read a bit about DNS failover and the consensus seemed to be that all DNS servers listed should return equal results since requests are spread round-robin between them (at least for mikrotik routers).
You are lucky I haven’t deleted my pi-hole VM yet ;D
In the Pi-Hole DNS settings I have the following configuration:
true,192.168.1.0/24,192.168.1.1,fritz.box
.
fritz.box
was my local DHCP domain name but has since been changed to lan
.The other settings in Pi-Hole were under the Local DNS Records menu where I added my domain name (let’s call it example.com) to the list of local DNS records and pointed it at the IP of the server running my reverse-proxy. Finally I added each subdomain I wanted to use to the List of local CNAME records and pointed it at the domain I just entered to the other list.
I can’t perfectly tell you what my router settings were unfortunately since I have recently moved and replaced my fritzbox with a mikrotik router. The main thing you have to do though is to go to the DHCP server settings of your router and set the pi-holes IP address as the DNS server. Note that in the case of the pi-hole being offline for any reason you will be unable to resolve any domains while in this network
It might be possible to do some sort of failover setup by running a second pi-hole with identical settings but I did not want my network connectivity depending on any device other than my router being on. Hence my move back to using my mikrotiks built-in DNS server which fortunately also supports adding lists for DNS adblocking.
I’m not the guy you replied to but personally I use a setup called split-horizon DNS.
This is a little bit of a simplification. I also use a cloudflare tunnel to allow access to select subdomains and I have 2 reverse-proxies chained together since NPM can resolve services by their container name as long as they are in the same docker network.
Also probably important: My DNS server was a pi-hole (until today at least) and did not act as my DHCP server. This meant it had no idea of local device hostnames and therefore was configured to forward queries to local device names to my routers built-in DNS server.
The domain I use for my services is one I rent from a registrar so that I can get valid SSL certificates without self-signing them. If you are fine with self-signed certificates or simple http you probably don’t need to do that.
I think I used a Pi 4B, either the 8 or 2 GiB model because that’s what I had lying around.
I never tried a compute module but instead upgraded to a lenovo tiny pc.
Also in my experience the raspberry pi isn’t all that great for a NAS considering you are reliant on using USB hard drives and also need a separate powered USB hub for them
I have also heard that you can bind your hypothetical torrent client to your hypothetical VPN network interface meaning it would be unable to even send out any data if the VPN was not connected.
Or in the case of docker use a prepackaged VPN+Torrent container or pipe all container network traffic through a VPN container like gluetun
The Arch-wiki was my main reason for switching to arch. When I used an ubuntu based distro I felt like I had to rely on forum posts to figure out anything whereas with arch everything is documented incredibly well
VLC can play blurays?