Your debug log is fine. However, there a a few things that could be "improved" and might be related to the issue you experience.
You distribute your Router's IP as DNS server via DHCP to your clients. You could change that to be the IP of your Pi-hole. Advantage would be that you see individual clients in your dashboard and could use the group management if needed.
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
Timeout: 10 seconds
* Received 335 bytes from wlan0:192.168.1.1
Offered IP address: 192.168.1.36
Server IP address: 192.168.1.1
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
domain-name: "home"
dns-server: 192.168.1.1
router: 192.168.1.1
You assigned an IPv6 with a global scope to your Pi-hole (2a01:XXX). This address might change, e.g. if you get a new IPv6 prefix from your ISP. If you need IPv6 within your lan, it's better to assing a ULA address.