A few problems noted in your debug log. Your router is at 192.168.170.1. Your Pi-Hole should be on this address range - it looks like it was setup to listen on address 192.168.170.43. But farther down in the log you have Pi-Hole IP set as 0.0.0.0 (NULL). This is incorrect. The Pi-Hole IP of xxx...43 will work, but you need to reconfigure Pi-Hole to listen at this IP.
The correct setup would be router at xxx.1, Pi-Hole at xxx.43 with a static IP. DNS on your router set to xxx.43 only (no second DNS). Turn off DNS rebind protection on your router.
*** [ DIAGNOSING ]: Networking
[✓] IPv4 address(es) bound to the eth0 interface:
192.168.170.43/24 does not match the IP found in /etc/pihole/setupVars.conf (https://discourse.pi-hole.net/t/use-ipv6-ula-addresses-for-pi-hole/2127)
*** [ DIAGNOSING ]: Name resolution (IPv4) using a random blocked domain and a known ad-serving domain
[✓] view.atdmt.com.66842.9517.302br.net is 0.0.0.0 via localhost (127.0.0.1)
[✓] view.atdmt.com.66842.9517.302br.net is 0.0.0.0 via Pi-hole (0.0.0.0)
[✓] doubleclick.com is 216.58.207.142 via a remote, public DNS server (8.8.8.8)
*** [ DIAGNOSING ]: Setup variables
PIHOLE_INTERFACE=eth0
IPV4_ADDRESS=0.0.0.0
IPV6_ADDRESS=0000:0000:0000:0000:0000:0000:0000:0000
A few helpful threads: