Web Interface only reachable via IP-Address

Help
1

Expected Behaviour:

I am on a raspberry pi 3A+, running raspberry pi OS. I was previously running pi-hole, unbound, and using pi-hole as a DHCP server. When I would go to http://pi.hole/admin/index.php I could access the web interface.

Actual Behaviour:

Suddenly I was unable to access the web interface on http://pi.hole/admin/index.php. I can still access it through http://PIHOLE-IP/admin. I believe this is because pi-hole is no longer the DNS Server on my router, but my settings still show it as the DNS server.

Debug Token:

https://tricorder.pi-hole.net/6q2cmbaV/

2

Run from the client that cannot access Pi-hole's UI by name, what is the output of:

nslookup pi.hole
3

Below is the result of that command

Server:		192.168.1.2
Address:	192.168.1.2#53

Name:	pi.hole
Address: 169.254.18.200
Name:	pi.hole
Address: fe80::cab6:208a:8397:213a

I also noticed, even though my Pi-hole's Static DHCP leases configuration says it should have an IP of 192.168.1.3 it has 192.168.1.2. When I turn off DHCP control in Pi-hole and on in my router, which has the pi-hole's static set to 192.168.1.3, it corrects. Is it possible I have the static set wrong within Pi-hole's DHCP control??

When I restart my Pi-hole I do get the error below.

DHCP packet received on wlan0 which has no address
no address range available for DHCP request via lo
4

There are two network interfaces on your Pi-hole host machine, each carrying a different IP address (as they should):

*** [ DIAGNOSING ]: Network interfaces and addresses
   2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
       inet 192.168.1.3/24 brd 192.168.1.255 scope global dynamic noprefixroute eth0
          valid_lft 85676sec preferred_lft 74876sec
   3: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
       inet 192.168.1.25/24 brd 192.168.1.255 scope global noprefixroute wlan0
          valid_lft forever preferred_lft forever

So at the time of debug log creation, 192.168.1.2 was not assigned to your Pi-hole host machine.

It is surprising that 192.168.1.2 is answering here, and it is unexpected that it would answer pi.hole with a link-local IPv4 address.
That may be related to your clients still assuming Pi-hole at 192.168.1.2 from a DHCP lease information acquired by your router, and your router still associating that IP with a MAC address of your Pi-hole's host machine.

When switching DHCP servers, you should force your clients to renew their DHCP lease with Pi-hole, e.g. by power-cycling them.

5

I set my DHCP server back to my router, and am still unable to access the http://pi.hole/admin/index.php interface. It seems to have corrected the IPs because when switching DHCP servers it reset all IPs on my network.

Strangely when I set my routers DNS server back to default, as in not the IP of the Pihole, I can now access the interface.

6

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