# Pihole Not Working on Other Devices using a ZyXEL router

**URL:** <https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608>\
**Category:** Help\
**Created:** [June 9, 2017, 10:51pm UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608 "2017-06-09T22:51:22Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![ribird](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/eb9ed0/32.png) [@ribird](https://discourse.pi-hole.net/u/ribird)\
**Post date:** [June 9, 2017, 10:51pm UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/1 "2017-06-09T22:51:22Z")

</div>

Pihole seems to be working correctly on my raspberrypi; however, I'm having trouble getting it to work on my other devices. My method of testing it has been to blacklist a website and checking to see if I can reach it on my other devices. I have tried changing the settings on my router, changing the DNS settings on my mac, and even turning of DHCP on my router and turning it on in settings on pi-hole/admin page, but so far no luck.  
Heres some pictures of where I have tried changing on my router:

 ![](https://discourse.pi-hole.net/uploads/default/original/3X/d/1/d19595473227be845413cdbc70d239d36fb4535b.png)  
 ![](https://discourse.pi-hole.net/uploads/default/original/3X/e/6/e697b5ecf5f284d19d4db88ad2323276de921ab6.png)

My pihole ip address is 192.168.1.4/24. I set the IP values under the DNS Values as you can see.  
I also tried this underneath broadband settings where it says DNS server 1:

 ![](https://discourse.pi-hole.net/uploads/default/original/3X/6/0/60304deac5a0d1c0b9a78cf937a19fbda663cd5f.png)  
Right now the values are just set to OpenDNS because the other method caused my internet to fail.

Here's what I got after running pihole -d:  
::: Beginning Pi-hole debug at Fri Jun 9 17:23:11 CDT 2017!  
:::  
::: This process collects information from your Pi-hole, and optionally uploads  
::: it to a unique and random directory on tricorder.pi-hole.net.  
:::  
::: NOTE: All log files auto-delete after 48 hours and ONLY the Pi-hole developers  
::: can access your data via the given token. We have taken these extra steps to  
::: secure your data and will work to further reduce any personal information gathered.  
:::  
::: Please read and note any issues, and follow any directions advised during this process.  
:::  
::: ---= Detecting Installed Package Versions:  
::: Pi-hole: v3.0.1 (master:v3.0.1-0-g26fcb1b)  
::: Pi-hole Dashboard: v3.0.1 (master:v3.0.1-0-ge204cea)  
::: lighttpd/1.4.35  
::: PHP 5.6.30-0+deb8u1 (cli) (built: Apr 14 2017 16:20:58)  
:::  
::: ---= Detecting existence of /etc/pihole/setupVars.conf:  
::: File exists, parsing...done and was successfully sourced  
:::  
::: ---= Detecting installed OS Distribution  
:::  
::: ---= Checking processor variety  
:::  
::: ---= Checking IPv6 Stack  
::: IPv6 addresses located on eth0  
::: No gateway detected.  
:::  
::: ---= Checking IPv4 Stack  
::: No IPv4 found on eth0  
:::  
::: ---= Daemon Process Information  
::: Checking http port for lighttpd listener.  
::: Correctly configured.  
:::  
::: ---= Daemon Process Information  
::: Checking domain port for dnsmasq listener.  
::: Correctly configured.  
:::  
::: ---= Daemon Process Information  
::: Checking 4711 port for pihole-FTL listener.  
::: Failure: IPv4 Port not in use  
:::  
::: ---= Processes Check  
::: Logging status of lighttpd, dnsmasq and pihole-FTL...  
:::  
::: ---= Resolver Functions Check (IPv4)  
::: Checking for necessary lighttpd files.  
:::  
::: ---= Detecting existence of /etc/lighttpd/lighttpd.conf:  
::: File exists, parsing...done  
:::  
::: ---= Detecting existence of /var/log/lighttpd/error.log:  
::: File exists, parsing...done  
:::  
:::  
::: ---= Detecting existence of /etc/dnsmasq.conf:  
::: File exists, parsing...done  
:::  
::: ---= Detecting contents of /etc/dnsmasq.d/\*:  
:::  
::: ---= File /etc/dnsmasq.d/01-pihole.conf found  
::: Parsing...done  
:::  
::: ---= File /etc/dnsmasq.d/03-pihole-wildcard.conf found  
::: Parsing...done  
:::  
::: ---= File /etc/dnsmasq.d/README found  
::: Parsing...done  
:::  
:::  
::: ---= Detecting existence of /etc/pihole/whitelist.txt:  
::: File exists, parsing...done  
:::  
::: ---= Detecting existence of /etc/pihole/blacklist.txt:  
::: File exists, parsing...done  
:::  
::: ---= Detecting existence of /etc/pihole/adlists.list:  
::: File exists, parsing...done  
:::  
::: ---= Analyzing gravity.list  
:::  
::: ---= Analyzing pihole.log  
:::  
::: ---= Analyzing pihole-FTL.log  
:::  
::: --= User Action Required =--  
::: Try loading a site that you are having trouble with now from a client web browser..  
::: (Press CTRL+C to finish logging.)  
:::  
::: ---= pihole.log  
::: Logging will automatically teminate in 60 seconds  
::: Finshed debugging!.

Thanks!

---

<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 9, 2017, 10:55pm UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/2 "2017-06-09T22:55:52Z")

</div>

Did you receive a token when the debug program finished? We need that to identify your log.

---

<div class="post-metadata">

**Author:** ![ribird](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/eb9ed0/32.png) [@ribird](https://discourse.pi-hole.net/u/ribird)\
**Post date:** [June 9, 2017, 11:15pm UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/4 "2017-06-09T23:15:52Z")

</div>

My token is: wzswetzipx

---

<div class="post-metadata">

**Author:** ![jayray](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/j/f19dbf/32.png) [@jayray](https://discourse.pi-hole.net/u/jayray)\
**Post date:** [June 10, 2017, 12:56am UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/5 "2017-06-10T00:56:53Z")

</div>

I notice that your IP range is 192.168.1.2 to 192.168.1.254. But your DNS servers are x.x.x4 and x.x.x.5. My guess is that some other device on your network has been served the same address as your PI. This is probably the cause of your troubles. You can check by looking around on your router GUI for the list of connected devices and the IPs they have been given.

An easy fix might be to change your IP range from x.x.x.2-254 to, say, x.x.x.10-254. (Mine starts at 100.) This way your DHCP clients wont get the same IP as your PI, mucking things up.

So shrink the IP range your router will serve up. Besides preventing duplicate IPs, you'll have room to expand with further networking devices down the line. Plenty of room for static client IPs and other networking devices such as PIs, NASes, media servers, vpns, etc.

By the way, what device is 192.168.1.5? Do you have a second Pihole or something?

---

<div class="post-metadata">

**Author:** ![ribird](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/eb9ed0/32.png) [@ribird](https://discourse.pi-hole.net/u/ribird)\
**Post date:** [June 10, 2017, 2:02am UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/6 "2017-06-10T02:02:02Z")

</div>

Thanks, I'll give it a try!  
No, I made me put a second IP address in so I used 192.168.1.5 because my Pi's was 192.168.1.4/24 so I figured it was within it's range. I'm not quite sure if thats how that works though. I'm new to a lot of this stuff, so I'm learning as I go.

---

<div class="post-metadata">

**Author:** ![ribird](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/eb9ed0/32.png) [@ribird](https://discourse.pi-hole.net/u/ribird)\
**Post date:** [June 10, 2017, 2:09am UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/7 "2017-06-10T02:09:58Z")

</div>

I have tried what you said, but unfortunately it has not resolved the issue. Any other ideas?

---

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [June 10, 2017, 2:40am UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/8 "2017-06-10T02:40:07Z")

</div>

From second screenshot, change "Beginning IP address" into 192.168.1.10.  
That leaves the lower 9 IP addresses to be assigned a static IP address.  
From second screenshot, delete the second DNS server entry "DNS Server 2" (leave blank) or else, ads will still come through.  
From third screenshot, leave as is or change back to default "Dynamic" DNS server.  
Reboot your own PC.

---

<div class="post-metadata">

**Author:** ![jayray](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/j/f19dbf/32.png) [@jayray](https://discourse.pi-hole.net/u/jayray)\
**Post date:** [June 10, 2017, 2:44am UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/9 "2017-06-10T02:44:13Z")

</div>

Yeah, I'm learning as I go as well. I'm not all that further ahead of you and still consider myself new to all this. I don't have any additional ideas, just furthering on this one.

Verify that your connected devices IPs have changed to reflect the new IP range you entered. Since DHCP leases are timed, some of the old IPs may still be active. Especially make sure that no device BUT the pihole has the x.x.x.4 address.

Also, I doubt this makes a difference to this problem, but if you can't completely eliminate that bogus x.x.x.5 address, I'd think about changing to something that doesn't have even the potential for a conflict. For example, 10.x.x.x.

---

<div class="post-metadata">

**Author:** ![ribird](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/eb9ed0/32.png) [@ribird](https://discourse.pi-hole.net/u/ribird)\
**Post date:** [June 10, 2017, 3:00am UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/10 "2017-06-10T03:00:06Z")

</div>

It won't let me leave it blank, so instead of put a b.s. ip address in their (10.1.1.1). For some reason it's still not working though.

---

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [June 10, 2017, 3:02am UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/11 "2017-06-10T03:02:23Z")

</div>

Put in the same address twice.  
So DNS1 and DNS2 point to Pi-Hole IP address 192.168.1.4.  
Whenever you make DHCP changes, reboot your own PC or disconnect/reconnect network!!!

---

<div class="post-metadata">

**Author:** ![ribird](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/eb9ed0/32.png) [@ribird](https://discourse.pi-hole.net/u/ribird)\
**Post date:** [June 10, 2017, 3:08am UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/12 "2017-06-10T03:08:01Z")

</div>

It wont let me put in the same addresa twice. Thanks for the tip though.

---

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [June 10, 2017, 3:11am UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/13 "2017-06-10T03:11:18Z")

</div>

If your router wont allow, only alternative I can think of is switching the DHCP server off/disabling on the router.  
And flip on the DHCP server on the Pi-Hole web admin page copying most of the settings from your router like start and end IP range etc.

> [@How do I use Pi-hole's built in DHCP server (and why would I want to)?](https://discourse.pi-hole.net/t/how-do-i-use-pi-holes-built-in-dhcp-server-and-why-would-i-want-to/3026):
>
> Using Your Existing Router For Network-wide Ad Blocking You might not need to use Pi-hole's DHCP server: In many home environments, your router also functions as your DHCP server. In this case, you can often [set Pi-hole to be the DNS server for your network clients in the router's DHCP (or LAN) settings page](https://discourse.pi-hole.net/t/how-do-i-configure-my-devices-to-use-pi-hole-as-their-dns-server/245), which allows all of your network clients to block ads simply by connecting to the network. Setting it up this way is also what makes Pi-hole very powerful for network-wide ad blocking. W…

---

<div class="post-metadata">

**Author:** ![ribird](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/eb9ed0/32.png) [@ribird](https://discourse.pi-hole.net/u/ribird)\
**Post date:** [June 10, 2017, 3:31am UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/14 "2017-06-10T03:31:19Z")

</div>

Yeah I tried that too. Unfortunately, that doesn't work either. I have even tried connecting my phone and computer directly to the DNS on the pi, but the internet won't work when I try that, so I'm not sure what the problem is.

---

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [June 10, 2017, 3:36am UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/15 "2017-06-10T03:36:36Z")

</div>

What is response from below on Pi-Hole ?

~~`nslookup -type=a pi-hole.net`~~  
`nslookup -type=a pi-hole.net 192.168.1.4`

And what is response from below on the PC once it receives its IP from Pi-Hole instead of the router ?

`nslookup -type=a pi.hole`

---

<div class="post-metadata">

**Author:** ![ribird](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/eb9ed0/32.png) [@ribird](https://discourse.pi-hole.net/u/ribird)\
**Post date:** [June 10, 2017, 3:53am UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/16 "2017-06-10T03:53:28Z")

</div>

From pi-hole:  
Server: 192.168.1.4  
Address: 192.168.1.4#53

Non-authoritative answer:  
Name: pi-hole.net  
Address: 104.24.108.83  
Name: pi-hole.net  
Address: 104.24.109.83  
From Mac:  
Server: 192.168.1.1  
Address: 192.168.1.1#53

\*\* server can't find pi.hole: NXDOMAIN

---

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [June 10, 2017, 3:55am UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/17 "2017-06-10T03:55:49Z")

</div>

Did you reboot the Mac after you switched DHCP server from router to that of Pi-Hole ?

This bit is wrong:

`Server: 192.168.1.1`

Should be:

`Server: 192.168.1.4`

---

<div class="post-metadata">

**Author:** ![ribird](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/eb9ed0/32.png) [@ribird](https://discourse.pi-hole.net/u/ribird)\
**Post date:** [June 10, 2017, 4:03am UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/18 "2017-06-10T04:03:31Z")

</div>

I just changed it manually in system preferences on my mac and get:  
;; connection timed out; no servers could be reached

---

<div class="post-metadata">

**Author:** ![ribird](https://discourse-cdn.pi-hole.net/letter_avatar_proxy/v4/letter/r/eb9ed0/32.png) [@ribird](https://discourse.pi-hole.net/u/ribird)\
**Post date:** [June 10, 2017, 4:04am UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/20 "2017-06-10T04:04:47Z")

</div>

That was it from my mac.

---

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [June 10, 2017, 4:06am UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/21 "2017-06-10T04:06:40Z")

</div>

Before you posted more info for the nslookup command :

> [@ribird](#):
>
> From Mac:  
> Server: 192.168.1.1  
> Address: 192.168.1.1#53

Where has this info gone ?

---

<div class="post-metadata">

**Author:** ![deHakkelaar](https://discourse-cdn.pi-hole.net/user_avatar/discourse.pi-hole.net/dehakkelaar/32/674_2.png) [@deHakkelaar](https://discourse.pi-hole.net/u/deHakkelaar)\
**Post date:** [June 10, 2017, 4:14am UTC](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608/22 "2017-06-10T04:14:14Z")

</div>

> [@ribird](#):
>
> ;; connection timed out; no servers could be reached

Above message makes me believe you configured network on mac manually and made a mistake.  
Please try to set mac to receive IP via DHCP and reboot?

[Next page](https://discourse.pi-hole.net/t/pihole-not-working-on-other-devices-using-a-zyxel-router/3608.md?page=2)