Adds visible in Roku, but setup used to work - Is the question mark in network tool related?

[Briare0s]

Debug token: Solved!

The issue I am facing:
I have Roku and a series of interfaces seemingly not going trough pihole and I'm not sure why. It used to work, but suddenly stopped.

Details about my system:
Using Pi-Hole as a addblocker and recursive dns via this video.
Runing pihole on a RB-pi retro.

Router runs DD-WRT.
Assigned static IP to all devices on network.
Used PiHole IP as static DNS.
Roku is behind a VPN via policy based routing in the router.

Topology:

internet -> router -> media server
******** |-> policy based routing vpn -> roku

What I have changed since installing Pi-hole:

Added blacklist / whitelist / regex.
Setup as recursive DNS.
Used this tutorial for setup.

Let me know if anything is missing.

[jfb]

"Questionmark in network tool"

Please provide more specifics. In addition to a text explanation, a screen capture of what you see would be helpful. In this forum, you can paste an image directly into a reply.

[Briare0s]

Thanks for the suggestion, also changed the title for clarity:

[jfb]

Your DHCP server (the router) is advertising itself as the DNS server, and not advertising Pi-hole.

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   Timeout: 10 seconds
   
   * Received 300 bytes from eth0:192.168.1.1
     Offered IP address: 192.168.1.150
     Server IP address: 192.168.1.1
     Relay-agent IP address: N/A
     BOOTP server: (empty)
     BOOTP file: (empty)
     DHCP options:
      Message type: DHCPOFFER (2)
      server-identifier: 192.168.1.1
      lease-time: Infinite
      netmask: 255.255.255.0
      broadcast: 192.168.1.255
      dns-server: 192.168.1.1
      hostname: "pihole"
      wpad-server: "
"
      router: 192.168.1.1
      --- end of options ---
    
   DHCP packets received on interface lo: 0
   DHCP packets received on interface eth0: 1

[Briare0s]

That was it, thanks so much for the help. Problem seems solved for now.

For those also using dd-wrt:

1. go to router settings
2. in Network Address Server Settings -> Turn on Use DNSMasq for DNS & save
3. in Services -> in Additional Dnsmasq Options add dhcp-option=6, your.static.pi.addr (fill in your own static pi addr at the end).
4. save, apply & reboot.
5. enjoy!

[RonV42]

Just a quick warning on blocking ads on Roku's. There are now many streaming services that if they can't use various google ad platforms will not function. I first discovered this with the Strr channel and would receive a "api failure" message, then Comet would randomly not come back from their commercial insertion. And some of the aggregation services have channels that will not load. I just gave up and had the Roku bypass the pi.hole ad blocks.

[Briare0s]

I found the same ron, but I managed to whitelist some individual links that got my apps to work again. I'd say, try this regex and whitelist when needed (as found it here):

(ads|captive|cloudservices|logs|sr|cs|web|api).roku(.admeasurement)*.com$