Pi-hole with AT&T router

Help
8

Your debug log is completely normal. This is the DNS traffic in the past 24 hours - Pi-Hole is blocking domains you have told it to block.

   [2020-01-16 15:57:25.712 5733] Imported 7439 queries from the long-term database
   [2020-01-16 15:57:25.713 5733]  -> Total DNS queries: 7439
   [2020-01-16 15:57:25.713 5733]  -> Cached DNS queries: 424
   [2020-01-16 15:57:25.714 5733]  -> Forwarded DNS queries: 2998
   [2020-01-16 15:57:25.714 5733]  -> Exactly blocked DNS queries: 4017
   [2020-01-16 15:57:25.714 5733]  -> Unknown DNS queries: 0
   [2020-01-16 15:57:25.714 5733]  -> Unique domains: 1116
   [2020-01-16 15:57:25.715 5733]  -> Unique clients: 5
   [2020-01-16 15:57:25.715 5733]  -> Known forward destinations: 2

Since you are still seeing ads, there are several possibilities.

  1. Some of the DNS traffic is not going to Pi-Hole, but is going elsewhere. Since the router is still performing a DHCP function, it may also be providing a non-Pi-Hole DNS path.

From a client that you believe should be connected to the Pi-Hole for DNS, from the command prompt or terminal on that client (and not via ssh or Putty to the Pi), what is the output of

nslookup pi.hole

if a PC, also include the output of ipconfig /all

  1. Some ads cannot be easily blocked by a domain blocker such as Pi-Hole. Typically YouTube and other services that serve ads from the same domain as the content. Can you provide an example URL where you are seeing ads?

These tools can also help determine where ads are coming from: