# Dashboard live but ads not blocked!

**URL:** <https://discourse.pi-hole.net/t/dashboard-live-but-ads-not-blocked/21186>\
**Category:** Help\
**Created:** [June 28, 2019, 5:18am UTC](https://discourse.pi-hole.net/t/dashboard-live-but-ads-not-blocked/21186 "2019-06-28T05:18:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![block\_head](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/b/278dde/32.png) [@block\_head](https://discourse.pi-hole.net/u/block_head)\
**Post date:** [June 28, 2019, 5:18am UTC](https://discourse.pi-hole.net/t/dashboard-live-but-ads-not-blocked/21186/1 "2019-06-28T05:18:05Z")

</div>

## Expected Behaviour:

I've installed pi-hole and logged into the dashboard. At this point, I would expect ads to be blocked at this point, but I can't figure out a way to achieve this.

## Actual Behaviour:

I've installed pi-hole and have access to the dashboard on my client. But ads are still showing up. I've disabled DHCP on my modem and enabled it on the pi dashboard. When I 'nslookup' by pi.hole or my pi address, I get a 'non-existent domain' response.

This has been a very frustrating experience. Woe is me 😿

## Debug Token:

https://tricorder.pi-hole.net/se1vb09vp5

---

<div class="post-metadata">

**Author:** ![block\_head](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/b/278dde/32.png) [@block\_head](https://discourse.pi-hole.net/u/block_head)\
**Post date:** [June 28, 2019, 5:24am UTC](https://discourse.pi-hole.net/t/dashboard-live-but-ads-not-blocked/21186/2 "2019-06-28T05:24:38Z")

</div>

So update on this: I am able to block ads on my iphone, just not on my Windows 10 desktop. I've blocked ipv6 and am still having issues.

---

<div class="post-metadata">

**Author:** ![block\_head](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/b/278dde/32.png) [@block\_head](https://discourse.pi-hole.net/u/block_head)\
**Post date:** [June 28, 2019, 6:06am UTC](https://discourse.pi-hole.net/t/dashboard-live-but-ads-not-blocked/21186/3 "2019-06-28T06:06:09Z")

</div>

Everything seems to be linked up fine. Not sure how it is getting blocked. I have pi-hole pointing towards 192.168.0.1 ... any idea why other devices are working but not my desktop?

![Screenshot%20(9)](https://discourse.pi-hole.net/uploads/default/original/2X/f/f9238ca0ee163e986180cc5d3e68cfcb5462a8db.png)

---

<div class="post-metadata">

**Author:** ![Mcat12](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/mcat12/32/20_2.png) [@Mcat12](https://discourse.pi-hole.net/u/Mcat12)\
**Post date:** [June 29, 2019, 12:52am UTC](https://discourse.pi-hole.net/t/dashboard-live-but-ads-not-blocked/21186/4 "2019-06-29T00:52:33Z")

</div>

Your debug log is clean and Pi-hole is blocking domains and responding to DNS queries. That means that your issues are with your client configurations. Your screenshot only shows the IP address info for your machine, the important setting is the DNS server. Make sure Pi-hole is the only DNS server.

> [@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…

---

<div class="post-metadata">

**Author:** ![system](https://discourse.pi-hole.net/uploads/default/original/3X/7/c/7c8792f649eeb921c5d2b4c41564ffa873d9a2b8.png) [@system](https://discourse.pi-hole.net/u/system)\
**Post date:** [July 20, 2019, 12:52am UTC](https://discourse.pi-hole.net/t/dashboard-live-but-ads-not-blocked/21186/5 "2019-07-20T00:52:37Z")

</div>

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.