Under your LAN and IP settings, you have defined the Pi-hole IP (10.0.0.30) as your sole DNS ?
Try disabling thr DNS cache:
Is your gateway using IPV6 DNS servers? If yes, try disabling the IPV6 on the wan side or set the IPV6 IP of the Pi-hole under ipv6 WAN dns:
this should not happen. The DHCP lease request should be answered regardless of incoming connection type by the Pi-hole.
If the router does not broadcast the requests originating from the WiFi clients then the issue is isolated to the Router.
Try setting the Pi-hole IP under WAN IP address / Select DNS type.
If you run this on a client and the IP resolves, your DNS request DID go through and it DID resolve properly.
So if you can “translate” a name into an IP , the DNS server (Pi-hole in this case) did the job.
If you CAN’T access pages, then the routing is messed up.
Where does it fail with a tracert/traceroute?