That look all good.
DNS is working and if you query a naughty domain, you'll notice it gets redirected to 0.0.0.0:
nslookup doubleclick.com 10.1.1.240
I wouldn't even bother trying to configure the Asus router to push the Pi-hole IP address for DNS resolution via DHCP to its clients as described here (method 1):
This because most Asus routers encountered push two DNS servers instead of only the Pi-hole IP address:
Better switch off the DHCP service on the Asus router and flip it on on Pi-hole:
But before that, try assign a lower static IP address to Pi-hole like for example 10.1.1.2 or 10.1.1.3.
That way you can set the DHCP range of IP addresses to be handed out to the clients (can alter later on web GUI) from lets say 10.1.1.10 up to 10.1.1.254
If you edit below file, you'll notice it has a section at the bottom with your interface and IP address.
If edit any, you'll need to reboot and run pihole -r reconfigure again (maybe with nameserver hack).
If you change IP address, make sure its not taken already by pinging the address first!
sudo nano /etc/dhcpcd.conf
If your interested if your Asus router's DHCP service behaves the same as hours:
sudo apt install nmap
sudo nmap -sU -p67 --script dhcp-discover 10.1.1.1