# Traffic not routing through pi-hole

**URL:** <https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775>\
**Category:** Help\
**Created:** [April 19, 2020, 4:29pm UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775 "2020-04-19T16:29:29Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [April 20, 2020, 9:49pm UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/22 "2020-04-20T21:49:37Z")

</div>

> [@Edwin\_Reik](#):
>
> Server: 192.168.1.1  
> Address: 192.168.1.1#53

Seems like your router's DHCP server is still active, distributing itself `192.168.1.1` as DNS server.

If your client is running Windows, you could verify this by running:

```auto
ipconfig /all | find /i "server"

```

---

<div class="post-metadata">

**Author:** ![Edwin\_Reik](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/edwin_reik/32/14213_2.png) [@Edwin\_Reik](https://discourse.pi-hole.net/u/Edwin_Reik)\
**Post date:** [April 20, 2020, 9:52pm UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/23 "2020-04-20T21:52:39Z")

</div>

The option is unchecked on in my router settings

---

<div class="post-metadata">

**Author:** ![Edwin\_Reik](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/edwin_reik/32/14213_2.png) [@Edwin\_Reik](https://discourse.pi-hole.net/u/Edwin_Reik)\
**Post date:** [April 20, 2020, 9:53pm UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/24 "2020-04-20T21:53:43Z")

</div>

no mac actually

---

<div class="post-metadata">

**Author:** ![Edwin\_Reik](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/edwin_reik/32/14213_2.png) [@Edwin\_Reik](https://discourse.pi-hole.net/u/Edwin_Reik)\
**Post date:** [April 20, 2020, 9:58pm UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/25 "2020-04-20T21:58:26Z")

</div>

here's ifconfig

 ![chrome_5grZpogoAs](https://discourse.pi-hole.net/uploads/default/original/2X/9/9a6e874bb4e0f673319907593d23c241e0fac382.png) ![vncviewer_q4k8HdHcUX](https://discourse.pi-hole.net/uploads/default/original/2X/b/bdf28cb510180d935f968e098ea0b405f19558be.png)

---

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [April 20, 2020, 10:16pm UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/26 "2020-04-20T22:16:32Z")

</div>

> [@Edwin\_Reik](#):
>
> The option is **unchecked on**

That sounds a bit contradictive - is it unchecked or on?

---

<div class="post-metadata">

**Author:** ![Edwin\_Reik](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/edwin_reik/32/14213_2.png) [@Edwin\_Reik](https://discourse.pi-hole.net/u/Edwin_Reik)\
**Post date:** [April 20, 2020, 10:21pm UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/27 "2020-04-20T22:21:59Z")

</div>

Unchecked

 ![vncviewer_u4w5VqPABV](https://discourse.pi-hole.net/uploads/default/original/2X/5/5bf6387d10b0472bc1b63fbed59a3295ea5dbc5a.png)

---

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [April 20, 2020, 10:39pm UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/28 "2020-04-20T22:39:47Z")

</div>

As _`nslookup`_ output clearly shows that your client is using your router for DNS, that means either your router is still running DHCP or your client hasn't renewed it's DHCP lease yet.

Can you ping your Pi-hole's IP from your Mac client?

---

<div class="post-metadata">

**Author:** ![Edwin\_Reik](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/edwin_reik/32/14213_2.png) [@Edwin\_Reik](https://discourse.pi-hole.net/u/Edwin_Reik)\
**Post date:** [April 20, 2020, 10:54pm UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/30 "2020-04-20T22:54:47Z")

</div>

![vncviewer_5bweAxKctg](https://discourse.pi-hole.net/uploads/default/original/2X/c/ca85dbbe049e10fc8e63928ec374e50e63b0f560.png)

---

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [April 20, 2020, 11:02pm UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/32 "2020-04-20T23:02:19Z")

</div>

You can ping Pi-hole, but not use it for DNS.

Do you run a firewall on your Pi-hole machine that would block [DNS or DHCP ports](https://docs.pi-hole.net/main/prerequesites/#ports)?

---

<div class="post-metadata">

**Author:** ![Edwin\_Reik](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/edwin_reik/32/14213_2.png) [@Edwin\_Reik](https://discourse.pi-hole.net/u/Edwin_Reik)\
**Post date:** [April 20, 2020, 11:08pm UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/33 "2020-04-20T23:08:52Z")

</div>

There's no firewall unless its built into raspbian.

I ran sudo lsof -i -P -n | grep LISTEN in case it might help.

 ![vncviewer_lPwSe1UPCF](https://discourse.pi-hole.net/uploads/default/original/2X/2/2af2b0dce253d602c8bbbfd6ac8ab4a270ade64c.png)

---

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [April 20, 2020, 11:27pm UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/38 "2020-04-20T23:27:45Z")

</div>

Thank you, but that just shows what ports are bound, not which ones are blocked - and part of that is already in your debug log anyway.  
By the way, you can check the log, it's located at `/var/log/pihole_debug.log` and it is meant to be consulted by users _and_ us for troubleshooting.

I just noticed I misspelled the second nslookup command.  
Could you rerun and post the output for:

```auto
nslookup flurry.com 192.168.1.11

```

And I've got help from a colleague with mac knowledge now to back me up.  
You could run the following on your Mac to show your DHCP server:

```auto
ipconfig getpacket en0 | grep "server_identifier"

```

You may have to change `en0` to `en1` if you use WiFi or Ethernet.

---

<div class="post-metadata">

**Author:** ![Edwin\_Reik](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/edwin_reik/32/14213_2.png) [@Edwin\_Reik](https://discourse.pi-hole.net/u/Edwin_Reik)\
**Post date:** [April 20, 2020, 11:37pm UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/41 "2020-04-20T23:37:50Z")

</div>

ipconfig:  
server\_identifier (ip): 192.168.1.1

nslookup:  
:: connection timed out; no servers could be reached

---

<div class="post-metadata">

**Author:** ![Bucking\_Horn](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/bucking_horn/32/18719_2.png) [@Bucking\_Horn](https://discourse.pi-hole.net/u/Bucking_Horn)\
**Post date:** [April 20, 2020, 11:47pm UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/42 "2020-04-20T23:47:04Z")

</div>

The first one shows your Mac is still seeing your router as DHCP, while the second confirms you cannot resolve DNS through Pi-hole.

Both could be explained by a firewall blocking DNS and DHCP ports.  
As you run a few additional software packages, those might have activated _`iptables`_ rules on your RPi.  
A quick test would be to run

```auto
sudo iptables -L

```

However, that is not the only possible firewall package, and configuration would depend on which one you run.

I am afraid I have to catch some sleep now, it is way past midnight for me (I am in Europe) - I'll ask my fellow team members to keep looking after you. 😉

@jfb, can you have a look here, please?

---

<div class="post-metadata">

**Author:** ![Edwin\_Reik](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/edwin_reik/32/14213_2.png) [@Edwin\_Reik](https://discourse.pi-hole.net/u/Edwin_Reik)\
**Post date:** [April 20, 2020, 11:51pm UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/44 "2020-04-20T23:51:52Z")

</div>

Thanks for your help!

---

<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:** [April 21, 2020, 12:05am UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/45 "2020-04-21T00:05:59Z")

</div>

Let's focus on the Mac and see what is using for DNS. If needed, we will manually map Pi-hole as DNS on this device and test that way. From the Mac terminal (and not via ssh session to the Pi-hole), what is the output of the following:

`cat /etc/resolv.conf | grep nameserver`

---

<div class="post-metadata">

**Author:** ![Edwin\_Reik](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/edwin_reik/32/14213_2.png) [@Edwin\_Reik](https://discourse.pi-hole.net/u/Edwin_Reik)\
**Post date:** [April 21, 2020, 12:17am UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/47 "2020-04-21T00:17:39Z")

</div>

cat call returns:  
nameserver 192.168.1.1

---

<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:** [April 21, 2020, 12:22am UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/48 "2020-04-21T00:22:16Z")

</div>

OK. This client is using the router as the nameserver, and it appears the router is not properly routing the DNS traffic to the Pi-hole. Let's bypass the router and go directly to Pi-hole for DNS.

_ **System preferences \> Network \> Advanced \> DNS** _.

Add the DNS server with the IP of your Pi-hole (and no others) - 192.168.1.11.

Click _ **OK** _, then click _ **Apply** _. Now the Mac should be using Pi-hole for DNS.

From the Mac terminal, run `nslookup pi.hole` and post the output.

---

<div class="post-metadata">

**Author:** ![Edwin\_Reik](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/edwin_reik/32/14213_2.png) [@Edwin\_Reik](https://discourse.pi-hole.net/u/Edwin_Reik)\
**Post date:** [April 21, 2020, 12:27am UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/49 "2020-04-21T00:27:24Z")

</div>

;; connection timed out; no servers could be reached

---

<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:** [April 21, 2020, 12:39am UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/50 "2020-04-21T00:39:16Z")

</div>

What nameserver is the Mac using now? Again from the Mac terminal:

`cat /etc/resolv.conf | grep nameserver`

If this shows that Pi-hole is the only DNS server, then the problem lies in your network configuration. Something is blocking DNS traffic from getting to the Pi-hole.

---

<div class="post-metadata">

**Author:** ![Edwin\_Reik](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/edwin_reik/32/14213_2.png) [@Edwin\_Reik](https://discourse.pi-hole.net/u/Edwin_Reik)\
**Post date:** [April 21, 2020, 9:40pm UTC](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775/51 "2020-04-21T21:40:33Z")

</div>

I get:

nameserver 192.168.1.1

[Previous page](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775.md?page=1)

[Next page](https://discourse.pi-hole.net/t/traffic-not-routing-through-pi-hole/30775.md?page=3)