Your DNS service IS working (IPV4 included) as per one of your screenshots, the IP of google.com was resolved by the DNS query.
The problem lies with routing, gateway settings maybe ?
As for IPV6, if both IPV6 and IPV4 are present (active) within a network, IPV6 is preferred.
I believe this is not related with Pi-hole or Unbound since everything in the screenshots, is showing that they work.
DNS is only there to "translate" google.com or whatever domain name one might want to access, to an IP (since a name is easier to remember than the IP address) and again, based on your screenshots, it seems to be doing just that.
How it connects AFTER it knows the translation, depends on the local settings/parameters/routing, things that are outside the scope and functionality of Pi-hole and unbound for that matter.
What happens if you put the IP that's resolved by ping in the browser?
So this is on a separate machine, 192.x.x.17, and I don't understand why this would happen. The .17 is asking the pi-hole (.11) for the IP of linode.com, the pi-hole forwards the IP to the .17 machine, and the .17 machine says that the request timed out. Why would this happen?
Too much confusing info for me.
The last screenshots you posted is missing the Reply column.
How have you concluded above and what do you mean by that ?
Are you talking about pings (ICMP) or DNS queries ?
Totaly makes no sense.
And are the routes working now on Pi-hole ?
ip -4 address
ip -6 address
ip -4 route
ip -6 route
traceroute -4n 8.8.8.8
traceroute -6n 2001:4860:4860::8888
The screenshots aren't helping either (prefer text output).
Try get the IP part working first on Pi-hole box and clients.
Troubleshoot DNS later.
Sorry if sounds bit harsh.
I use nslookup on a random pc in my house via Windows command line. Looking up the ip of linode.com. The pihole web console clearly shows the query from my random computer (. 17) and says that the answer is forwarded to that machine. While the actual machine says the pihole timed out.
$ 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
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual nameservers.
nameserver 127.0.0.1
search Hogwarts.academy
options edns0
$ echo 'nameserver 8.8.8.8' | sudo tee /etc/resolv.conf
[sudo] password
nameserver 8.8.8.8
$ nslookup pi-hole.net
;; connection timed out; no servers could be reached
$
Thanks for your help. I decided to remove unbound and start fresh. Upon reinstalling pi-hole after fully removing, I now have a new issue. You can find it here: Lighttpd 403 admin page - #3 by Jorgsmash