![](/static/61a827a1/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/8286e071-7449-4413-a084-1eb5242e2cf4.png)
2·
11 months agoSorry 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.
My method to get around this is setting up a specific user account for my TV. In the user options you can disable transcoding
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