From what we can see there should not be any issues(i stand corrected on my post above). Is there something that is working that shouldn't be or vvice versa right now?
default via 192.168.178.1 dev enp4s0 proto static metric 100
169.254.0.0/16 dev enp4s0 proto kernel scope link src 169.254.140.105 metric 202
192.168.178.0/24 dev enp4s0 proto kernel scope link src 192.168.178.21 metric 100
I don't know what this address is: 169.254.0.0/16 dev
I have VirtualBox installed, maybe for it?
IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.178.1 0.0.0.0 UG 100 0 0 enp4s0
169.254.0.0 0.0.0.0 255.255.0.0 U 202 0 0 enp4s0
192.168.178.0 0.0.0.0 255.255.255.0 U 100 0 0 enp4s0
I don't know what "169.254.0.0 0.0.0.0 255.255.0.0 U 202 0 0 enp4s0" is...
nslookup 192.168.178.21 (pihole address)
** server can't find 21.178.168.192.in-addr.arpa: NXDOMAIN
Networking
[✓] IPv4 address(es) bound to the enp4s0 interface:
192.168.178.21/24 matches the IP found in /etc/pihole/setupVars.conf
169.254.56.37/16 does not match the IP found in /etc/pihole/setupVars.conf (Use IPv6 ULA addresses for Pi-hole)
[✗] No IPv6 address(es) found on the enp4s0 interface.
[i] Default IPv4 gateway: 192.168.178.1
Pinging 192.168.178.1...
[✓] Gateway responded.
[4711] is in use by pihole-FTL
[5333] is in use by pihole-FT
[53] is in use by dnsmasq
[9050] is in use by tor
[9665] is in use by java
[9666] is in use by java
[513] is in use by dnscrypt-
[513] is in use by systemd
[5333] is in use by pihole-FT
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
dig: '' is not a legal name (unexpected end of input)
[✗] Failed to resolve via localhost (127.0.0.1)
dig: '' is not a legal name (unexpected end of input)
[✗] Failed to resolve via Pi-hole (192.168.178.21)
[✓] doubleclick.com is 172.217.16.78 via a remote, public DNS server (8.8.8.8)
WHY???
[✗] Failed to resolve via localhost (127.0.0.1)
[✗] Failed to resolve via Pi-hole (192.168.178.21)