After pihole update DNS resolution is not available

[Fox-Jet]

Hello,
I updated my Pihole to the latest version, but at the end of the update I got the message:
"DNS resolution is not available".
I use pihole on a Raspi pi 1 and it is connected via LAN with the router.

After searching the internet, I found an article in this section where someone has the same problem and was able to solve it by editing the 'resolv.conf' -> nameserver 127.0.0.1. Unfortunately this file already looks like in the post (DNS resolution is currently unavailable).

So I started the update process again and got the message

Retrieval of supported OS list failed. dig failed with return code 10. 
      Unable to determine if the detected OS (Raspbian 10) is supported
......
 If you are seeing this message after having run pihole -up:
             sudo PIHOLE_SKIP_OS_CHECK=true pihole -r
           (In this case, your previous run of pihole -up will have already updated the local repository)

So I ran the command and got the message:

Downloading and Installing FTL
   Error: URL https://github.com/pi-hole/ftl/releases/latest/download/pihole-FTL-armv6-linux-gnueabihf not found
  [✗] FTL Engine not installed

  Unable to complete update, please contact Pi-hole Support

Long story short, is there anyone who can help me get rid of this problem?

Thanks in advance
Fox-Jet

[jfb]

You want your Pi nameserver to be something other than Pi-hole. This allows the Pi to connect to the internet when Pi-hole is not working (as in your case).

sudo nano /etc/resolv.conf

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

Run pihole -r and select repair.

[Fox-Jet]

@jfb

sudo nano /etc/resolv.conf

It worked perfect.
Thanks a lot!

BR Fox-Jet

[jfb]

Note that this nameserver change is temporary. To make the change permanent, you will need to edit the source file that populates /etc/resolv/conf.

[Fox-Jet]

However, this problem shouldn't happen again with the next update, right?
As I understand it, the problem only occurs if the set DNS server cannot be reached during the update, right?

Fox-Jet

[Fox-Jet]

@jfb yes no maybe?

[jfb]

@Fox-Jet

this problem shouldn't happen again with the next update, right?

As long as the nameserver of the Pi is pointing to Pi-hole, you run the risk of an update problem if Pi-hole is not working properly.

By permanently changing the nameserver to a public DNS, you maintain the ability for the Pi to reach the internet always. This could be for time server updates, Pi-hole updates or debug logs, OS updates, etc.

If you don't browse the web using the Pi, I recommend changing the nameserver to a public DNS. Do it once and you don't have to worry about it again.