That might explain the problem. Assuming adguard returns an nxdomain for blocked sites then the devices will try with their secondary DNS server and get to the blocked site

Sorry I misread your post. You shouldn’t need the 172 address in your DNS config, stick to the 127 address only.

In regard to the issue itself. Do your devices show their DNS server as the adguard server?

Your adguard config looks strange. The examples shown list different DNS providers but you have pointed it back at itself for its DNS. I don’t understand why you would do that.

I have a similar setup using Truenas to store data. I’ve setup a VM in Truenas that can access the data via NFS (easier to setup on Linux than SMB).

It’s nice to keep all your services contained in one machine, as long as it has enough resources, and will probably consume less power than running another PC.

I use qbittorrent, most people seem to agree it performs better than Transmission. It’s accessible from a web interface.

Higher end cable testers can show you where the break is, but it will be far more expensive that a new cable.

It depends how valuable your data is, what backup strategy you have, and how long you’re prepared to wait to get access to your data when a drive fails.

Personally if/when I migrate my main dataset to SSD, I’ll stick with RAIDZ2/RAID6.

I’ve seen a few people recommending paperless-ngx

deleted by creator

Install Windows Subsystem for Linux and pretend windows doesn’t exist

This is an interesting problem and probably one I will run into when I eventually divide my LAN into multiple vlans.

Unless traffic can be filtered based on hostname then the only solution I can think of is to run two instances of the proxy/ingress controller.