'fail to fetch' and DNS related issues? Topic is solved

[MichaIng]

@trendy
Ah, which image do/did you use? I remember one report and already removed/reset the resolvconf head on that particular image to be empty. It is definitely not wanted but was shipped by the pre-image, not recognised by me since the default DNS on DietPi was 1.1.1.1 as well (as long as not overridden via DHCP), now 9.9.9.9 btw.

Finally new images from now on are shipped without resolvconf, as it is not required, which resolves such issue on the basic level. However it can be installed to use its features without breaking anything.

[trendy]

Last time I came across it was in the raspberry and the rockpi.
I downloaded the raspberry image about a month ago and the rockpi a couple of months ago.

[Joulinar]

@trendy
Don't mix the DNS/Ping connectivity check with the DNS resolution setting for the network interface. These are 2 different thinks. On the Rpi image, it was never the case. I'm using DHCP on all my RPi's and they all use my PiHole. Non of them is going to a hard coded 1.1.1.1 DNS server.

@Mattie
It would be good to know what exactly your issue is. Is it DNS resolution or connectivity? I doubt it's similar to the original reported issue.

[trendy]

I'm using DHCP on all my RPi's and they all use my PiHole. Non of them is going to a hard coded 1.1.1.1 DNS server.

Are you also hijacking the queries that try to bypass the pihole?

[Joulinar]

there are no queries bypassing PiHole. All my RPi's using just one singel DNS Server

Code: Select all

root@DietPi3:~# cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 192.168.0.11
search lan
root@DietPi3:~#

Code: Select all

root@DietPi3:~# cat /etc/resolvconf/resolv.conf.d/head
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
#     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
root@DietPi3:~#

[trendy]

I just downloaded them again.
In Raspberry image there isn't anything, so I could be wrong or it was fixed.
In RockPi image there is still nameserver 1.0.0.1 in /etc/resolvconf/resolv.conf.d/head

[Mattie]

for me it was openvpn messing it up, it worked when i disabled the vpn service

[MichaIng]

@trendy
Thanks for the hint, it is the ROCK Pi 4 image, right? I'll fix and repack that.