Web interface does not resolve via http://pi.hole only by http://<ip address>

Help
1

Pihole was working fine using Router DHCP server, but I would like to see more details about which clients are hitting which external traffic sources. So I enabled the Pihole DHCP server.

:white_check_mark: Router DHCP disabled
:white_check_mark: Pihole DHCP enabled

Expected Behaviour:

Visiting http://pi.hole/admin in a browser via a connected device will bring you to the admin panel

Actual Behaviour:

http://pi.hole does not resolve, displays error

This site can’t be reached

pi.hole ’s server IP address could not be found.

Try:

DNS_PROBE_FINISHED_BAD_CONFIG

Pihole admin console is only available via http://<ipaddress>/admin

Debug Token:

Also discovered that pihole is unable to upload debug logs... https://paste.ubuntu.com/p/xxfXPv7wZP/

2

After you changed DHCP servers, did you reboot the router and renew the DHCP leases on all connected clients?

3

This in your debug output caught my eye:

   Jun  5 04:46:15 dnsmasq-dhcp[1235]: DHCP, IP range 192.168.6.1 -- 192.168.6.1, lease time 2m
   Jun  5 04:46:15 dnsmasq-dhcp[1235]: DHCP, IP range 192.168.7.1 -- 192.168.7.1, lease time 2m
   Jun  5 04:46:15 dnsmasq-dhcp[1235]: DHCP, IP range 192.168.1.2 -- 192.168.1.251, lease time 1d

It looks like IP's are trying to be handed out on three different IP ranges, only the last of which matches your network configuration. What is the output of the following command from the Pi terminal (checking your dnsmasq configuration files):

sudo grep -v '#\|^$' -R /etc/dnsmasq.*

4

Result of that command:

/etc/dnsmasq.conf:conf-dir=/etc/dnsmasq.d
/etc/dnsmasq.conf.old:conf-dir=/etc/dnsmasq.d
/etc/dnsmasq.d/02-pihole-dhcp.conf:dhcp-authoritative
/etc/dnsmasq.d/02-pihole-dhcp.conf:dhcp-range=192.168.1.2,192.168.1.251,24h
/etc/dnsmasq.d/02-pihole-dhcp.conf:dhcp-option=option:router,192.168.1.1
/etc/dnsmasq.d/02-pihole-dhcp.conf:dhcp-leasefile=/etc/pihole/dhcp.leases
/etc/dnsmasq.d/02-pihole-dhcp.conf:domain=lan
/etc/dnsmasq.d/02-pihole-dhcp.conf:dhcp-rapid-commit
/etc/dnsmasq.d/02-pihole-dhcp.conf:dhcp-option=option6:dns-server,[::]
/etc/dnsmasq.d/02-pihole-dhcp.conf:dhcp-range=::100,::1ff,constructor:eth0,ra-names,slaac,24h
/etc/dnsmasq.d/02-pihole-dhcp.conf:ra-param=*,0,0
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/local.list
/etc/dnsmasq.d/01-pihole.conf:addn-hosts=/etc/pihole/custom.list
/etc/dnsmasq.d/01-pihole.conf:localise-queries
/etc/dnsmasq.d/01-pihole.conf:no-resolv
/etc/dnsmasq.d/01-pihole.conf:cache-size=10000
/etc/dnsmasq.d/01-pihole.conf:log-queries
/etc/dnsmasq.d/01-pihole.conf:log-facility=/var/log/pihole.log
/etc/dnsmasq.d/01-pihole.conf:local-ttl=2
/etc/dnsmasq.d/01-pihole.conf:log-async
/etc/dnsmasq.d/01-pihole.conf:server=9.9.9.9
/etc/dnsmasq.d/01-pihole.conf:server=149.112.112.112
/etc/dnsmasq.d/01-pihole.conf:interface=eth0
/etc/dnsmasq.d/01-pihole.conf:server=/use-application-dns.net/
/etc/dnsmasq.d/01-pihole.conf:dhcp-name-match=set:hostname-ignore,wpad
/etc/dnsmasq.d/01-pihole.conf:dhcp-name-match=set:hostname-ignore,localhost
/etc/dnsmasq.d/01-pihole.conf:dhcp-ignore-names=tag:hostname-ignore
/etc/dnsmasq.d/SoftAp0:interface=usb0
/etc/dnsmasq.d/SoftAp0:interface=usb1
/etc/dnsmasq.d/SoftAp0:port=53
/etc/dnsmasq.d/SoftAp0:dhcp-authoritative
/etc/dnsmasq.d/SoftAp0:domain-needed
/etc/dnsmasq.d/SoftAp0:bogus-priv
/etc/dnsmasq.d/SoftAp0:expand-hosts
/etc/dnsmasq.d/SoftAp0:dhcp-range=usb0,192.168.7.1,192.168.7.1,2m
/etc/dnsmasq.d/SoftAp0:dhcp-range=usb1,192.168.6.1,192.168.6.1,2m
/etc/dnsmasq.d/SoftAp0:listen-address=127.0.0.1
/etc/dnsmasq.d/SoftAp0:listen-address=192.168.7.2
/etc/dnsmasq.d/SoftAp0:listen-address=192.168.6.2
/etc/dnsmasq.d/SoftAp0:dhcp-option=usb0,3
/etc/dnsmasq.d/SoftAp0:dhcp-option=usb0,6
/etc/dnsmasq.d/SoftAp0:dhcp-option=usb1,3
/etc/dnsmasq.d/SoftAp0:dhcp-option=usb1,6
/etc/dnsmasq.d/04-pihole-static-dhcp.conf:dhcp-host=44:61:32:E0:21:A1,192.168.1.12,ecobee
/etc/dnsmasq.d/04-pihole-static-dhcp.conf:dhcp-host=44:61:32:84:51:56,192.168.1.201,ecobee-camera
/etc/dnsmasq.d/04-pihole-static-dhcp.conf:dhcp-host=00:80:92:A1:6C:B7,192.168.1.100,BRW008092A16CB7
/etc/dnsmasq.d/04-pihole-static-dhcp.conf:dhcp-host=20:DF:B9:D4:08:2B,192.168.1.101,Google-Home-Mini
/etc/dnsmasq.d/04-pihole-static-dhcp.conf:dhcp-host=F4:F5:D8:A2:16:FC,192.168.1.102,Google-Home
/etc/dnsmasq.d/04-pihole-static-dhcp.conf:dhcp-host=7C:66:9D:53:6C:33,192.168.1.16,beaglebone
/etc/dnsmasq.d/04-pihole-static-dhcp.conf:dhcp-host=44:61:32:29:82:11,192.168.1.202,ecobee-camera2
/etc/dnsmasq.d/04-pihole-static-dhcp.conf:dhcp-host=58:7A:62:26:B7:04,192.168.1.103,genie
6

Rebooting solved most of the issues but dns name resolution is slow and a few clients still state they have no dns resolution.

7

Please post a new debug token.

8

These SoftAP configuration files typically cause problems with Pi-hole. The settings here interfere with your Pi-hole settings. Move this file out of the dnsmasq.d subdirectory (don't just rename it in the same directory) and restart FTL with sudo service pihole-FTL restart

9

Since this is installed on a Beaglebone, it recreates the SoftAP0 file on reboot no matter what you do, even if you comment out the offending sections.

The only way I could get it to stop modifying the file (the duplicate dnsmasq.leases file was causing issues previously) is to use chattr +i to make the file immutable.

In this case, I truncated the file and made it immutable so that the file exists but can't be overwritten by the system. Pihole seems to be working okay now.

10

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