Pi hole admin page and queries no longer intercepted from PC

Help
1

Hi,
I just replaced my ADSL router by a Fiber Router.
I have pi-hole running from a raspberry pi for ages.
It seems I have messed something while migrating as my Win10 PC no longer seems to intercept queries. I think I have 2 issues, I'm rather brain-fried, if someone could give me a hint, it will be much appreciated:

Expected Behaviour:

When I type http://pi.hole/admin I should access the admin interface.

Actual Behaviour:

It does not work, I dont have the admin page.
Same as curl -I pi.hole (run from the raspberry pi using SSH)
curl: (6) Could not resolve host: pi.hole

Notes:
1)This works:
raspberrypi/admin/queries.php
192.168.2.3/admin

  1. I have renamed at somepoint the hostname to be rasperrypi... Maybe that explains something.
    .
    .
    .
    The second issue is that none of my queries run from the PC are intercepted.
    I type for example http://lequipe.fr.

Expected Behaviour:

In the query page (http://192.168.2.3/admin/queries.php); I should see a new entry.

Actual Behaviour:

I don't see any new query for that request.

Notes:
-I use chrome and I have disabled "securedns" a while ago, I checked it's still off.
-I have set in the new router the DNS server to be: hostname: raspberrypi.local and ip 192.168.2.3
-I have done ipconfig /flushdns from PC
-I restarted every devices
-I have done pihole -r to repair.
-It seems other clients have some intercepted queries I see the logs increasing.

From the PC, I dont like the look of this:
nslookup raspberrypi.local
Server: sunrise.box
Address: 192.168.2.1

Name: raspberrypi.local
Address: 192.168.2.3

I don't see why it's saying sunrise.box, as it was the default DNS entry from the router, which I deleted, and rebooted the router. Yet it's still visible...

Edit: I forgot to mention, from the new fiber router admin page, there is a diagnostic page.
I tried to nslookup "raspberrypi.local"; here what is the output:
Server: 127.0.0.1
Address 1: 127.0.0.1 wpad.sunrise.box

Name: raspberrypi.local
Address 1: 192.168.2.3 raspberrypi.local
iplist: 192.168.2.3

Ping also works, and traceroute:
traceroute to raspberrypi.local (192.168.2.3), 30 hops max, 38 byte packets
1 raspberrypi.local (192.168.2.3) 0.867 ms

Debug Token:

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

Can someone please help?
Thanks in advance,

2

Hi, I noticed I had "IPV6 LAN" ( LAN IPv6 Mode Setup) activated in the new fiber router, I deactivated that.
Still no change.

3

Today, from the computer with Win10:

nslookup www.google.com
Server: sunrise.box
Address: 192.168.2.1

Non-authoritative answer:
Name: www.google.com
Addresses: 2a00:1450:400a:800::2004
142.250.203.100

I think that router might be buggy, because it shows "sunrise.box" which was the old entry I deleted in the "network settings/DNS".
There there is only "raspberrypi.local" now.

I did the "ipconfig /flushdns" from the pc, etc... It seems something wrong.

4

Run from your Windows client, what's the output of:

nslookup pi.hole

nslookup flurry.com
5 
nslookup pi.hole
Server:  sunrise.box
Address:  192.168.2.1

*** sunrise.box can't find pi.hole: Non-existent domain

nslookup flurry.com
Server:  sunrise.box
Address:  192.168.2.1

Non-authoritative answer:
Name:    flurry.com
Addresses:  98.136.103.23
          212.82.100.150
          74.6.136.150

Edit: If I may add:

nslookup raspberrypi.local
Server:  sunrise.box
Address:  192.168.2.1

Name:    raspberrypi.local
Address:  192.168.2.3
6

That client isn't using Pi-hole as DNS server, but your router at 192.168.2.1.

This is also confirmed by your debug log, showing your router is distributing its own IP as DNS server:

*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
   Scanning all your interfaces for DHCP servers
   
   * Received 308 bytes from eth0:192.168.2.1
     Offered IP address: 192.168.2.3
     DHCP options:
      Message type: DHCPOFFER (2)
      router: 192.168.2.1
      domain-name: "sunrise.box"
      dns-server: 192.168.2.1
      --- end of options ---

You'd have to configure your router to make use of Pi-hole, preferably by distributing Pi-hole as local DNS server via DHCP - see Making your network take advantage of Pi-hole.

7

I agree, I came to the same conclusion.
But in the fiber router, I did define pihole as dns server, see:

8

In this forum, you can paste images directly.

You'd have to consult your router's documenation and support for details on its configuration.

9

Sure, I think it's somehow not configurable.

Thanks for the link, it's true, I should have that option as DHCP.
The problem is I can't change that apparently it seems buggy.

Capture3
Capture31268×236 6.71 KB

See, it's greyed out (I can't even click Static)

Capture2
Capture21392×898 41.7 KB

I will check with router config guide.

Tx again.

10

I'd probably start by checking the manual for details about the DNS Values section. The Static option under that heading may be what you are searching for.

If it doesn't work, you may consider switching off your router's DHCP and enabling Pi-hole's DHCP server instead.

11

Thanks,
I agree, thats what I would have configured but it's greyed out, not editable.
I will check with the router guide and write the outcome here after.
At least it's not a pi.hole issue :slight_smile:

PS: regarding the admin interface, is it because I changed the host name that I can't reach pi.hole/admin?

12

No, that's because Pi-hole is the only DNS server that would know to resolve pi.hole. Other DNS servers will just return NXDOMAIN.

13

Maybe it's worth something to anyone else, the router guide, regarding DNS is this manufacturer guide:
Zyxel guide:
The ISP guide for that device has been modified a bit:
ISP guide for the same device

There are 3 options:
1)Select DNS Proxy if you have the DNS proxy service. The Zyxel Device redirects clients' DNS
queries to a DNS server for resolving domain names.
-> I have that one by default, it's clearly not working.

2)Select Static if you have the static DNS service.
-> that one is always greyed out, unable to select.

3)DNS Server 1/2
Enter the first and second DNS (Domain Name System) server IP addresses the Zyxel Device passes to the DHCP clients.
-> That option is where one could set, for example 8.8.8.8 and 7.7.7.7 or whatever, or even pi.hole ip like 192.168.2.3 in my local network. Unfortunately it's buggy and greyed out.
Worse, in my case it was renamed "From ISP/ DNS Server 1 /DNS Server 2)" and it's greyed out like unable to change:

Capture3
Capture31268×236 6.71 KB

I have already contacted the ISP, who will ask their "expert". Unfortunately it means weeks of waiting, if they even call me back...

14

I kept doing research and reading.

I have basically 3 options:

  1. Router 1 (DHCP server) -> Router 2. That was/is my current setup, one big subnet.
  2. Router 1 -> Router 2 (DHCP server). I would have to change the WAN ip of router 2 to be router 1 local IP.
  3. Router 1/Router 2/ Pi-hole (DHCP server). <-- I'm not keen on that option. Especially when I have 2 expensive devices :slight_smile:

Still thinking of the pro/cons.

In the meantime I called the ISP again, and I send them the information about DNS changes from their latest and newest Zyxel Fiber router, they will contact me back. They looked serious this time, I got an email to send more information also.

15

I'm actually wondering what would be the pi-hole local domain name?

https://www.manualslib.com/manual/1864676/Zyxel-Communications-Ex5501-B0.html?page=189&term=dns&selected=6#manual
I have tested with raspberrypi.local (192.168.2.3).

That is reachable from the router.

aaaaaaaaae
aaaaaaaaae1729×571 39.7 KB

16

After digging and continuing configuration on the modem/router side, it seems something weird:
I was able to configure the static IP for the DNS in the dhcp section to be 192.168.2.3.
The modem/router can ping that address.
But- Once doing so, it's not working, my dns queries are not resolved and/if it does, it seems to be coming from the router:
Server: 127.0.0.1
Address 1: 127.0.0.1 wpad.sunrise.box

Name: www.gazeta.pl
Address 1: 80.252.0.145 host-80-252-0-145.gazeta.pl
iplist: 80.252.0.145

Sometimes it's not even picking up (still from the router):
nslookup www.google.com
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.2.1

I know it seems more of a router integration issue, I still trying to wonder with pi-hole:
Could it be because somehow the router might enforce ipv6 only (theory)?
I do not have ipv6 enabled in pi-hole.

I'm trying to understand why that device is not sending DNS queries to pi-hole...
(I have no queries in pi-hole during those tests).

17

Hi,
I have redesigned my networking and I have now the 2nd router receiving the internet from the first ISP's router. Internet worked.
As soon as I set the DNS server to be 192.168.2.3 (which is my local pi-hole server), the internet is gone.
See from my win10 client:

nslookup www.lequipe.fr
Server: UnKnown
Address: 192.168.2.2

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
^C
C:\Users\JS>nslookup pi.hole
Server: UnKnown
Address: 192.168.2.2

Name: pi.hole
Addresses: fe80::c17d:2a5:8688:5760
192.168.2.3

It's very strange to me.
The ISP is not helping, Does it makes sense to anyone that because I use pi-hole on my LAN; from my own router, it ends up disconnecting me from the internet???
What sorted of weird "shared" 10G fiber connection is that??

18

I think it's like this:
Internet -> ISP Router -> Netgear Router -> pi -hole ....-> Another DNS Server (1.1.1.1).

That results in no internet probably because it's actually doing:
Internet -> ISP Router -> Netgear Router -> windows pc -makes DnS query> pi -hole ....-> Netgear Router ->ISP router -> Another DNS Server (1.1.1.1).

Very strange to me.

19

CaptureDNS
CaptureDNS601×677 37.2 KB

20

Setting pi-hole (192.168.2.3) in "Use these DNS Servers" (as primary) result in no internet connection.
(yet during that time, I can see my win10 client, www.google.com, query is visible in pi-hole admin: that proves pi-hole works and it's ok on my network side).