Your DHCP server (the router) is not passing the Pi-hole IP as DNS. As a result, clients are not using Pi-hole for DNS, they are using the assigned DNS servers from the router.
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
* Received 296 bytes from wlan0:192.168.1.1
Offered IP address: 192.168.1.7
Server IP address: N/A
Relay-agent IP address: N/A
BOOTP server: (empty)
BOOTP file: (empty)
DHCP options:
Message type: DHCPOFFER (2)
server-identifier: 192.168.1.1
lease-time: 86400 ( 1d )
renewal-time: 43200 ( 12h )
rebinding-time: 75600 ( 21h )
netmask: 255.255.255.0
router: 192.168.1.1
domain-name: "home"
dns-server: 62.240.110.198
dns-server: 62.240.110.197
--- end of options ---
DHCP packets received on interface wlan0: 1
DHCP packets received on interface lo: 0
this is pi.hole
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.12
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
this is flurry.com
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.12
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
this is flurry.com 192.168.1.12
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 192.168.1.12
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
I Get This When I Ping The 192.168.1.12
Pinging 192.168.1.12 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.12:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
This doesn't look like it's related to Pi-hole:
A failing ping would suggest a network issue, which seems in line with your ERR_ADDR_UNREACHABLE message from your earlier screenshot from one of your clients.
Assuming a 192.168.1.0/24 subnet, at least your Windows client at 192.168.1.11 seems to be on the same network as your Pi-hole host machine at 192.168.1.12.
You should check your router for possible reasons why it wouldn't route packets to your Pi-hole machine.
Maybe you've assigned that .12 IP address twice, or your subnet mask is not a /24, or your router has enabled a feature like wifi client isolation, preventing wifi clients from being able to communicate with other machines in your network.