OpenDNS not Working via PiHole

[Zack]

Expected Behaviour:

Hi, I've been using PiHole for a couple years, and now looking to add OpenDNS as my children are starting to use devices on their own now. My router DHCP DNS settings are pointing at my PIHole Server. I've selected OpenDNS for IPv4 in PiHole DNS settings. My expectation is that PIHole would use OpenDNS as the DNS server, and block inappropriate content.

Actual Behaviour:

Content is not blocked.
Going to Welcome.OpenDNS states that I am not using OpenDNS
Running dnsleaktest extended test shows that I am still running thru my ISP DNS servers (8 in total).

If I change my router DNS to OpenDNS instead of PiHole:
Content is blocked.
Going to Welcome.OpenDNS.Com states that I am using OpenDNS
Running dnsleakstest extended test shows that I am going thru OpenDNS (1 server).

pihole diag.txt (31.7 KB)

[DanSchaper]

What is your docker-compose.yml or your docker run command line?

If you go to the admin webpage you will see the warnings icon that shows Pi-hole is ignoring queries. This is because the proper environment variables have not been set.

This also means that your client(s) are using another DNS server that is not Pi-hole.

[Zack]

Thanks for getting back to me. I was following these directions (https://www.techaddressed.com/tutorials/install-pi-hole-docker/)
and used the following:

version: "3"

services:
  pihole:
    container_name: pihole
    image: pihole/pihole:latest
    ports:
      - "53:53/tcp"
      - "53:53/udp"
 #      - "67:67/udp"  # Required only for using Pi-hole as a DHCP server
      - "8080:80/tcp"
    environment:
      TZ: 'America/New_York'
      WEBPASSWORD: 'xxx'
    volumes:
      - './etc-pihole:/etc/pihole'
      - './etc-dnsmasq.d:/etc/dnsmasq.d'
    cap_add:
      - NET_ADMIN
    restart:
      unless-stopped

[Zack]

You are correct, Pi Hole is not working as expected. It was uBlock that was blocking the CNN ads.

[Zack]

So I tried another memory card and just loaded PIHole without docker. It is working as expected. I'll probably just leave it as is. If you are interested in troubleshooting the docker version, I can load it anytime.