Hello,
I ran into an issue where my PiHole can't resolve DNS on eth0/enxb827ebad9642 but tun0 & openvpn clients can. I've tried changing the interface settings via the GUI but no change. I ended up spinning up a new PiHole for now but would like to get everything running on the original setup.
It has been running solid for over a year with its previous versions and stopped within minutes of updating to Pi-hole v5.8.1 FTL v5.13 Web Interface v5.10.1
I've run through the forums and have been unable to find a solution. Hopefully, some kind soul will help point me in the right direction.
Much appreciate your time and guidance.
pi@PiHole-VPN:~ $ hostnamectl
Static hostname: PiHole-VPN
Icon name: computer
Machine ID: ef052a6fa2f345e6852b1e3d197fecc1
Boot ID: 965e3034183444679a68733b12d971fe
Operating System: Raspbian GNU/Linux 9 (stretch)
Kernel: Linux 4.19.66-v7+
Architecture: arm
pi@PiHole-VPN:~ $
pi@PiHole-VPN:~ $ ifconfig
enxb827ebad9642: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.10.2 netmask 255.255.255.0 broadcast 192.168.10.255
inet6 fe80::8242:322c:b21a:471f prefixlen 64 scopeid 0x20
ether b8:27:eb:ad:96:42 txqueuelen 1000 (Ethernet)
RX packets 16045072 bytes 10336026950 (9.6 GiB)
RX errors 0 dropped 44984 overruns 0 frame 0
TX packets 10678904 bytes 9708826640 (9.0 GiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 1000 (Local Loopback)
RX packets 533755 bytes 35757798 (34.1 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 533755 bytes 35757798 (34.1 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 10.8.0.1 netmask 255.255.255.0 destination 10.8.0.1
inet6 fe80::9ce3:2f7a:e984:15b8 prefixlen 64 scopeid 0x20
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC)
RX packets 2790113 bytes 606021558 (577.9 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 7335798 bytes 8426643795 (7.8 GiB)
TX errors 0 dropped 295063 overruns 0 carrier 0 collisions 0
pi@PiHole-VPN:~ $
pi@PiHole-VPN:~ $ nslookup pi.hole 127.0.0.1
Server: 127.0.0.1
Address: 127.0.0.1#53
Name: pi.hole
Address: 127.0.0.1
pi@PiHole-VPN:~ $ nslookup pi.hole 192.168.10.2
;; connection timed out; no servers could be reached
pi@PiHole-VPN:~ $ nslookup pi.hole 10.8.0.1
Server: 10.8.0.1
Address: 10.8.0.1#53
Name: pi.hole
Address: 10.8.0.1
pi@PiHole-VPN:~ $ nslookup cnn.com 127.0.0.1
Server: 127.0.0.1
Address: 127.0.0.1#53
Name: cnn.com
Address: 0.0.0.0
pi@PiHole-VPN:~ $ grep -C5 cnn.com /var/log/pihole.log
Feb 6 08:43:51 dnsmasq[1285]: Pi-hole hostname pi.hole is 127.0.0.1
Feb 6 08:44:18 dnsmasq[1285]: query[A] pi.hole from 10.8.0.1
Feb 6 08:44:18 dnsmasq[1285]: Pi-hole hostname pi.hole is 10.8.0.1
Feb 6 08:44:24 dnsmasq[1285]: query[A] flurry.com from 127.0.0.1
Feb 6 08:44:24 dnsmasq[1285]: gravity blocked flurry.com is 0.0.0.0
Feb 6 08:44:59 dnsmasq[1285]: query[A] cnn.com from 127.0.0.1
Feb 6 08:44:59 dnsmasq[1285]: gravity blocked cnn.com is 0.0.0.0
pi@PiHole-VPN:~ $