![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
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?
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.
Jellyfin? It’s always supported 4K afaik
And if you’re looking for a way to simplify the setup process: borgmatic
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
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