It seems to have rotted a bit, but still does a good job. I just use OpenWRT's standard "Network" → "DHCP and DNS" → "List of domains to force an IP address" (and force them to 127.0.0.1).
But yeah, the Roku Express is nigh-unusable without DNS ad-blocking.
I redirect port 53 requests at the router to my internal AdGuard or PiHole, and I'm in the process of making a block list of IP addresses that are known DNS servers.
I have one little hole so that the AdGuard and PiHole can upstream their DNS requests to one or two IP addresses. Anything else is blocked or redirected. Of course, this doesn't cover more modern DNS queries that go over ports other than 53. A problem to be looked into in the near future.
Is this an ad for next DNS? Why not just block Roku in all the other local dns server options; you know pi hole? Some routers can do this too themselves.
My blocklist for Roku Express is
It seems to have rotted a bit, but still does a good job. I just use OpenWRT's standard "Network" → "DHCP and DNS" → "List of domains to force an IP address" (and force them to 127.0.0.1).But yeah, the Roku Express is nigh-unusable without DNS ad-blocking.
Surprising that this works. Many vendors hardcode DNS resolve or IP addresses into their software to prevent this
I redirect port 53 requests at the router to my internal AdGuard or PiHole, and I'm in the process of making a block list of IP addresses that are known DNS servers.
I have one little hole so that the AdGuard and PiHole can upstream their DNS requests to one or two IP addresses. Anything else is blocked or redirected. Of course, this doesn't cover more modern DNS queries that go over ports other than 53. A problem to be looked into in the near future.
Is this an ad for next DNS? Why not just block Roku in all the other local dns server options; you know pi hole? Some routers can do this too themselves.