# Unable to get the Pihole to block ads

**URL:** <https://discourse.pi-hole.net/t/unable-to-get-the-pihole-to-block-ads/13606>\
**Category:** Help\
**Created:** [October 11, 2018, 9:17am UTC](https://discourse.pi-hole.net/t/unable-to-get-the-pihole-to-block-ads/13606 "2018-10-11T09:17:26Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![jfb](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/jfb/32/4332_2.png) [@jfb](https://discourse.pi-hole.net/u/jfb)\
**Post date:** [October 11, 2018, 3:01pm UTC](https://discourse.pi-hole.net/t/unable-to-get-the-pihole-to-block-ads/13606/3 "2018-10-11T15:01:16Z")

</div>

Your debug log shows no problems with Pi-Hole that keeps it from blocking ads. In particular, this section of your debug log shows that it is working properly resolving DNS queries.

```
*** [DIAGNOSING]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] adwarehitman.com is 0.0.0.0 via localhost (127.0.0.1)
[✓] adwarehitman.com is 0.0.0.0 via Pi-hole (192.168.0.13)
[✓] doubleclick.com is 172.217.4.206 via a remote, public DNS server (8.8.8.8)

```

This problem is likely due to another DNS path to a third party DNS either on your router or client(s). With two DNS entries, the DNS traffic will go to both; some will go to Pi-Hole and some will bypass the Pi-Hole.

A quick way to check this is to use a client (desktop or laptop is usually a good choice), and assign that client with a manual DNS of Pi-Hole IP and nothing else. Clear the DNS cache on that client and then tail the pihole.log (Web Admin GUI \> Tools \> Tail pihole.log) and see if the traffic from that client is getting to the Pi-Hole.

> [@Why should Pi-hole be my only DNS server?](https://discourse.pi-hole.net/t/why-should-pi-hole-be-my-only-dns-server/3376):
>
> Reduced Ad Blocking Capability The main reason you should Pi-hole as your only DNS server is that you will see increased performance in the blocking of ads. If you have two DNS servers (Pi-hole and something else), your network clients may not always query Pi-hole for name resolution. If a query happens to be answered from a non-Pi-hole DNS server, your block lists will not apply (since that DNS server doesn't know about them). All Queries Need To Go Through Pi-hole First Since other DNS serv…

> [@How do I configure my devices to use Pi-hole as their DNS server?](https://discourse.pi-hole.net/t/how-do-i-configure-my-devices-to-use-pi-hole-as-their-dns-server/245):
>
> Three methods Generally, there are three different methods that will enable devices on your network to be protected by Pi-hole. 1. Define Pi-hole's IP address as the only DNS entry in the router Rationale Only is italicized here for a reason: Pi-hole needs to be the only DNS server because it intercepts queries and decides whether or not they should be blocked. If you have other DNS servers configured, you may be sent to the correct domain, bypassing Pi-hole completely. Because of this, we re…

---

_[View the full topic](https://discourse.pi-hole.net/t/unable-to-get-the-pihole-to-block-ads/13606)._