- DietPi version | v8.12.1
- Distro version | bullseye
- Kernel version | Linux DietPi 5.15.76-v8+ #1597
- SBC model | RPi 3 Model B
My RPi stopped connecting to the internet after I updated it and PiHole. I had everything set up and running with PiHole and it was all working. My wife started complaining about things on her phone not working on the WiFi such as TikTok comments or Facebook. The TV apparently doesn’t connect to Netflix and the XBox can’t connect to Live. My phone and computer have 0 issues accessing anything.
I updated the RPi, which is when it stopped connecting to anything. I tried all the fixes that I could find on the internet and this forum. Nothing worked so I reinstalled DietPi, and it’s the same as before except now it can’t perform the initial setup. I’ve restarted my router and modem. I changed the DNS settings in my router to Cloudflare.
During the dietpi-update command, the DNS resolver fails with exit code 2.
ping google.com says “Temporary failure in name resolution”
ping 1.1.1.1 doesn’t work
ping 9.9.9.9 works
I have the DNS set to cloudflare on the RPi.
What else can I do to get my RPi back on the internet? Is there a way to downgrade versions? Or is it possibly my ISP causing all these problems?
looks like you have issues connecting to Cloudfare. Could be your ISP blocking it or a temp issue within your region. I recommend switching to Quad9 as upstream DNS server. You are using static or DHCP on DietPi? If static, go to dietpi-config to change upstream DNS to Quad9. If DHCP, something to adjust on the DHCP server. BTW, you should do same on your router if DNS resolution with Cloudflare is not working atm.
Apparently my firewall is causing all this trouble. I will still try switching to Quad9 to see if my firewall messes with it.
facing the same issue when trying to reinstall netdata. Noted that as soon all services are stopped, dns does down. I am getting dns from my router and my router is getting dns from pi-hole.
it’s definitely a different issue. Is PiHole running on same system as DietPi is?
Yes. Whenever I try to reinstall a software it get stuck on apt update
Following service are avaiable on dietpi-service
proftpd : active | Affinity 0-3 │
│ nmbd : active | Affinity 0-3 │
│ smbd : active | Affinity 0-3 │
│ redis-server : active | Affinity 0-3 │
│ mariadb : active | Affinity 0-3 │
│ php7.4-fpm : active | Affinity 0-3 │
│ nginx : active | Affinity 0-3 │
│ qbittorrent : active | Affinity 0,1,2,3 │
│ jellyfin : active | Affinity 0-3 │
│ sonarr : active | Affinity 0-3 │
│ radarr : active | Affinity 0-3 │
│ bazarr : active | Affinity 0-3 │
│ prowlarr : active | Affinity 0-3 │
│ netdata : active | Affinity 0-3 │
│ webmin : active | Affinity 0-3 │
│ docker : active | Affinity 0-3 │
│ cron : active | Affinity 0-3 │
│ dropbear : active | Affinity 0-3 │
│ fail2ban : active | Affinity 0-3 │
│ pihole-FTL : active | Affinity 0-3 │
│ openvpn : active | Affinity 0-3 │
│ dietpi-vpn : inactive | Affinity 0-3 │
│ dietpi-cloudshell : inactive | Affinity 0-3 │
│ unpackerr : active | Affinity 0-3 │
│ ombi : active | Affinity 0-3 │
│ notifiarr : active | Affinity 0-3 │
│ cross-seed : active | Affinity 0-3 │
│ qbit-manage : active | Affinity 0-3 │
│ qbittools : active | Affinity 0-3 │
│ cloudflared : active | Affinity 0-3
I added cloudflared service to dietpi-service that could be the issue. Will check now. My stupid mistake. It is resolved now.
you should use Static IP an DietPi device as it is your main DNS server. Next to this choose a global upstream DNS within Static IP settings, to avoid issues with local DNS resoulution on DietPi system itself.