Expected Behaviour:
working DNS resolution on pi-hole:
ping -c 4 www.google.com
PING www.google.com(fra16s12-in-x04.1e100.net (2a00:1450:4001:818::2004)) 56 data bytes
64 bytes from fra16s12-in-x04.1e100.net (2a00:1450:4001:818::2004): icmp_seq=1 ttl=57 time=17.2 ms
...
Actual Behaviour:
no internet access from pi-hole
ping -c 4 www.google.com
ping: www.google.com: Temporary failure in name resolution
Debug Token:
0mu1n5r7w4
Dear community,
I am using pi-hole on a Raspberry Pi 2. It is running an openhabian linux distribution, based on Raspbian 9 (stretch) for smart home automation. Everything was working fine until my last apt-get upgrade command which broke DNS resolution. All clients in the network can access websites but without ad filtering.
According to /var/log/apt/history.log.1.gz the package openresolv was removed and replaced by resolvconf during the upgrade.
I also attached the content of history.log.1.gz here:
Start-Date: 2018-08-08 10:34:53
Commandline: apt-get -o APT::Status-Fd=4 -o APT::Keep-Fds::=5 -o APT::Keep-Fds::=6 --yes --no-install-recommends install resolvconf
Requested-By: openhabian (1000)
Install: resolvconf:armhf (1.79)
Remove: openresolv:armhf (3.8.0-1)
End-Date: 2018-08-08 10:35:15
Start-Date: 2018-08-08 10:53:11
Commandline: apt-get upgrade
Requested-By: openhabian (1000)
Upgrade: perl-base:armhf (5.24.1-3+deb9u3, 5.24.1-3+deb9u4), libc-ares2:armhf (1.12.0-1+deb9u1, 1.14.0-1~bpo9+1), libraspberrypi-bin:armhf (1.20180417-1, 1.20180703-1), libcups2:armhf (2.2.1-8, 2.2.1-8+deb9u2), libraspberrypi-dev:armhf (1.20180417-1, 1.20180703-1), libraspberrypi-doc:armhf (1.20180417-1, 1.20180703-1), php7.0-cgi:armhf (7.0.27-0+deb9u1, 7.0.30-0+deb9u1), php7.0-cli:armhf (7.0.27-0+deb9u1, 7.0.30-0+deb9u1), gnupg-agent:armhf (2.1.18-8~deb9u1, 2.1.18-8~deb9u2), git-man:armhf (1:2.11.0-3+deb9u2, 1:2.11.0-3+deb9u3), libsystemd0:armhf (232-25+deb9u2, 232-25+deb9u4), pi-bluetooth:armhf (0.1.7, 0.1.8), php7.0-opcache:armhf (7.0.27-0+deb9u1, 7.0.30-0+deb9u1), perl-modules-5.24:armhf (5.24.1-3+deb9u3, 5.24.1-3+deb9u4), php7.0-common:armhf (7.0.27-0+deb9u1, 7.0.30-0+deb9u1), git:armhf (1:2.11.0-3+deb9u2, 1:2.11.0-3+deb9u3), udev:armhf (232-25+deb9u2, 232-25+deb9u4), php7.0-sqlite3:armhf (7.0.27-0+deb9u1, 7.0.30-0+deb9u1), libmagic1:armhf (1:5.30-1+deb9u1, 1:5.30-1+deb9u2), libudev1:armhf (232-25+deb9u2, 232-25+deb9u4), raspberrypi-kernel:armhf (1.20180417-1, 1.20180703-1), dirmngr:armhf (2.1.18-8~deb9u1, 2.1.18-8~deb9u2), libperl5.24:armhf (5.24.1-3+deb9u3, 5.24.1-3+deb9u4), raspberrypi-bootloader:armhf (1.20180417-1, 1.20180703-1), dpkg:armhf (1.18.24, 1.18.25), libuv1:armhf (1.9.1-3, 1.18.0-3~bpo9+1), php7.0-json:armhf (7.0.27-0+deb9u1, 7.0.30-0+deb9u1), libmagic-mgc:armhf (1:5.30-1+deb9u1, 1:5.30-1+deb9u2), php7.0-readline:armhf (7.0.27-0+deb9u1, 7.0.30-0+deb9u1), bluez-firmware:armhf (1.2-3+rpt5, 1.2-3+rpt6), systemd-sysv:armhf (232-25+deb9u2, 232-25+deb9u4), libgcrypt20:armhf (1.7.6-2+deb9u2, 1.7.6-2+deb9u3), gpgv:armhf (2.1.18-8~deb9u1, 2.1.18-8~deb9u2), libpam-systemd:armhf (232-25+deb9u2, 232-25+deb9u4), shared-mime-info:armhf (1.8-1, 1.8-1+deb9u1), systemd:armhf (232-25+deb9u2, 232-25+deb9u4), libraspberrypi0:armhf (1.20180417-1, 1.20180703-1), file:armhf (1:5.30-1+deb9u1, 1:5.30-1+deb9u2), openhab2:armhf (2.2.0-1, 2.3.0-1), ca-certificates:armhf (20161130+nmu1, 20161130+nmu1+deb9u1), perl:armhf (5.24.1-3+deb9u3, 5.24.1-3+deb9u4), libhomegear-node:armhf (0.1.6-22, 0.1.7-25), gnupg:armhf (2.1.18-8~deb9u1, 2.1.18-8~deb9u2), libipc-run-perl:armhf (0.94-1, 0.94-1+deb9u1), libdpkg-perl:armhf (1.18.24, 1.18.25), patch:armhf (2.7.5-1, 2.7.5-1+deb9u1), dpkg-dev:armhf (1.18.24, 1.18.25), tzdata:armhf (2018c-0+deb9u1, 2018e-0+deb9u1)
End-Date: 2018-08-08 11:04:09
Could this be the cause for the broken DNS resolution? What would you recommend me to get pi-hole working again?
Thank you very much for all ideas
Kind regards,
ping