Expected Behaviour:
I recently had my entire apartment electricity cut out ( 1 in 10k, actual circuit breaker itself was faulty) which has happened 1-3 times in the past with no issue(turns out it was this problem for years). For some reason this time when things came back up, the internet didn’t “work”. The only time I’ve experienced this since I set up my pihole in 2018 was when the actual plug got pulled on the pihole. So unsure of what to do, i ran pihole -up.
I then was getting an error about DNS server failure, and an NTP error, and when I looked at ports in use I found someone who was having the same issue where their ConnMan was causing issues.
I followed steps to stop connman from using port 53 here, https://wiki.archlinux.org/title/ConnMan#Avoiding_conflicts_with_local_DNS_server
but I think I ended up just fouling up my pihole completely. The net is working but I am seeing adds even as I went about updating to some better gravity lists. I hadn’t changed lists either in years, as I worship at the alter of if it aint broke dont fix it.
- I am on raspberry Pi Bullseye
- I have the latest Pihole, FTL
Actual Behaviour:
when I run nslookup I get a return from the website, and then DNS request timed out.
I see clients being logged in my taillog on the pihole ui, and I see my pihole as the dns on my router but now I think I screwed up the connman setting.
Debug Token:
While typing this and trying to fix it myself, I ran pihole -r but that didn’t fix it.
The first token is prior to running pihole -r
https://tricorder.pi-hole.net/OUTUJ21f/
second is current.