Hello. I am not terribly sophisticated about Linux, so I apologize if my concerns are easy or hard to understand. I have been running pihole on my raspberry pi for about two years. I recently updated my raspberry pi to the latest version release called "bullseye". Since that update, my pihole installation is not working.
When I login to the pihole interface, I see a red dot that says "DNS service not running". I clicked on settings, and I see this error message:
PHP error (2): fsockopen(): unable to connect to 127.0.0.1:4711 (Connection refused) in /var/www/html/admin/scripts/pi-hole/php/FTL.php:44
You have a port 53 conflict - another service preventing pihole-FTL from binding to port 53:
*** [ DIAGNOSING ]: Pi-hole diagnosis messages
count last timestamp type message blob1 blob2 blob3 blob4 blob5
------ ------------------- -------------------- ------------------------------------------------------------ -------------------- -------------------- -------------------- -------------------- --------------------
1 2022-07-25 17:24:18 DNSMASQ_CONFIG failed to create listening socket for port 53: Address alrea
dy in use
*** [ DIAGNOSING ]: Ports in use
[✗] udp:127.0.0.1:53 is in use by connmand (https://docs.pi-hole.net/main/prerequisites/#ports)
udp:0.0.0.0:68 is in use by dhcpcd
Thank you. I discovered this is a known issue with the connman service on raspberry pi. I think I cleared this issue, but I am still having problems getting to webpages. I am getting timed out errors.
Something is interfering with DNS traffic to/from the ethernet port on the Pi:
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] o.bluewin.ch is 0.0.0.0 on lo (127.0.0.1)
[✗] Failed to resolve o.bluewin.ch on eth0 (192.168.1.2)
[✓] No IPv4 address available on wlan0
[✓] o.bluewin.ch is 0.0.0.0 on tun0 (10.8.0.1)
[✓] doubleclick.com is 142.250.69.238 via a remote, public DNS server (8.8.8.8)
Your router distributes it's own IP address as DNS server via DHCP. You should change that so that all devices use Pi-hole instead. Note: Pi-hole should be the only DNS server distributed via DHCP.
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
* Received 314 bytes from eth0:192.168.1.1
Offered IP address: 192.168.1.2
Server IP address: N/A
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.1.1
lease-time: 86400 ( 1d )
netmask: 255.255.255.0
router: 192.168.1.1
dns-server: 192.168.1.1
renewal-time: 43200 ( 12h )
rebinding-time: 75600 ( 21h )
domain-name: "localdomain"
--- end of options ---
DHCP packets received on interface lo: 0
DHCP packets received on interface wlan0: 0
DHCP packets received on interface eth0: 1
After you changed DHCP settings, you need to disconnect clients from the network to pickup the new settings.
To see if your Pi-hole is responding you could run
nslookup pihole 192.168.1.2` from one of your clients.
Thank you again for all your help. I had recently upgraded my raspberry pi software, and I suspected that was the issue. I did a clean install of the raspberry software and a clean install of raspberry pi, and everything is working great!