Updated and FTL failed, cannot resolve addresses

[PSteward]

Hello!

Updated my pi-hole to the latest version today (pi-hole -up) and it failed at FTL and cannot resolve addresses anymore. It appears it's own DNS is dead (dig anything doesn't work), I cannot find out where it is configured (no resolve.conf file / empty) and all other posts I read don't have this odd issue.
When I try the repair it fails just fails at GitHub as it cannot get the ip (dns fail). Dnsmasq is missing (should it be there??).
Not sure what happened but it seems to of messed up its own DNS during the update and didn't finish the update because of that.

Thanks,

--PSteward

[jfb]

Please follow our help template.

In particular, you have not provided a debug token.

[PSteward]

Hey Jfb,

I have no DNS. It won't upload as it fails connecting to tricorder.pi-hole.net.

Thanks,

--Phil Steward

[jfb]

This will temporarily reset the nameserver on the Pi to bypass Pi-Hole DNS.

sudo nano /etc/resolv.conf

Edit the nameserver line to nameserver 9.9.9.9 or your preferred third party DNS service, save and exit

Run

pihole -d

and upload the debug log.

[PSteward]

Hey JFB,

There is no resolv.conf, I saw a resolv.conf@ but everything is empty. Added nameserver and it doesn't work and with a reboot it erased again.

Thanks,

--PSTEWARD

[jfb]

PM me the debug log. It is located at

/var/log/pihole/pihole_debug.log

[PSteward]

Hey Jfb,

I ran:
sudo systemctl enable systemd-resolved && sudo systemctl start systemd-resolved
This allowed me then to run:
pihole -r and update to bullseye, then -r again and -d....
Here is the debug token:
https://tricorder.pi-hole.net/gfR6hglt/

Thanks,

--PSteward

[badjoodani]

After an update you might have lost your default route.

Please check your route "sudo route -v" if you don't have a default route
that got wiped on an update somehow. It should be something like what is below:

Kernel IP routing table
default fire 0.0.0.0 UG 0 0 0 ens160
192.168.xxx.x 0.0.0.0 255.255.255.0 U 0 0 0 ens160

TO fix it run "sudo route add default gw xxx.xxx.xxx.xxx"
substitute xxx.xxx.xxx.xxx for your firewall, router , etc, something such as "192.168.1.1"

[PSteward]

Hello badjoodani,

My routing is fine now. I even went and reinstalled everything including Debian from scratch but I still can't start FTL and dns is offline. The DNS of the unit is working however as I can resolve domain with curl/dig.

https://tricorder.pi-hole.net/QLDHy7xh/ <--Newest debug token.

Thanks,

--PSteward

[PSteward]

Anyone?

[deHakkelaar]

Upload another debug log and post a fresh token pls?
Retention for the logs on the tricorder server is 48 hours.