@johnpoz said in Streaming is being blocked on Roku:
You have no name on your views.. so yeah can see why it would balk at that.
access-control-view: <IP netblock> <view name> Set view for given access control element.And you shouldn't have that 2nd server: in there either.
Wouldn't it be just easier to assign your roku a different dns, say 8.8.8.8 - not sure why your roku would need to resolve anything on your local network anyway.
Thank you all for the responses.
EDIT: I had to go back and edit my original reply. I realized I am forcing DNS requests over CloudFlare 1.1.1.2 and 1.1.1.1. I also have two NICs and two different LANS, 192.168.1.0 and 10.1.1.1
I changed the Resolver code:
server: access-control-view: 192.168.1.0/24 dnsbl #All devices on this subnet run through pfBlockerNG DNSBL access-control-view: 192.168.1.121/32 bypass #Roku IP is bypassing pfBlockerNG DNSBL view: name: "bypass" view-first: yes view: name: "dnsbl" view-first: yes include: /var/unbound/pfb_dnsbl.*confHowever, I am noticing that ads are allowed for everything on 10.1.1.1 unless I add
access-control-view: 10.1.1.1/24 dnsbland the full code looks like this:
server: #All devices on this subnet run through pfBlockerNG DNSBL access-control-view: 192.168.1.0/24 dnsbl access-control-view: 10.1.1.1/24 dnsbl #Roku IP is bypassing access-control-view: 192.168.1.121/32 bypass pfBlockerNG DNSBL view: name: "bypass" view-first: yes view: name: "dnsbl" view-first: yes include: /var/unbound/pfb_dnsbl.*confApologies for the delay in responding, I never got any email notifications that I received responses to my original post. Weird.