Pi-hole is a domain blocker. If Pi-hole receives a query for a DNS domain, it will block that domain per your settings regardless of whether the queries are for the A record (IPv4) or AAAA record (IPv6) for the domain.
As an example, cnn.com is not blocked and Pi-hole will return either the A or the AAAA record.
Okay, I have, for example, googleads.g.doubleclick.net and www.googleadservices.com blocked. However, ads keep loading from those sites. I read somewhere that turning off IPV6 on a workstation would eliminate the problem. I tried that and it worked on my Windows 10 laptop. When I turned IPV6 back on, the ads returned. So, I assumed that there was a setting in Pi-hole that I would need to enable to block IPV6 DNS queries. I'm missing something here.
Configuration for interface "Local Area Connection* 1"
DNS servers configured through DHCP: fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Register with which suffix: Primary only
Configuration for interface "Wi-Fi"
** DNS servers configured through DHCP: None**
** Register with which suffix: Primary only**
Configuration for interface "Loopback Pseudo-Interface 1"
Statically Configured DNS Servers: fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
Register with which suffix: Primary only
Okay. I flushed DNS. I made sure DHCP was not serving DNS through the router. Still no luck. If, for example, I go to cnn.com, google ads loads the stupid banner. Do I need to move DHCP to the Pi-Hole to make this work?
Your results suggest you neither have public IPv6 connectivity in your network nor does your Windows client use your router's link-local IPv6 address as DNS server.
Run from your Windows laptop, what's the output of
Which links to googleadservices.com. It's not just CNN either. But when I disabled IPV6 on my laptop it stops. Okay, no biggie. I could just do that. However, my spouse's Samsung tablet doesn't let you disable IPV6, so it's ad city on that. And there are other devices in the house that I'd have to run around trying to disable IPV6 on. I just don't get how these ads are getting through.
Both of your debug logs indicate you do not have public IPv6 connectivity.
However, your older debug log showed your router to distribute its own IPv4 address as DNS server alongside Pi-hole:
*** [ DIAGNOSING ]: Discovering active DHCP servers (takes 10 seconds)
Scanning all your interfaces for DHCP servers
* Received 304 bytes from eth0:192.168.111.1
Offered IP address: 192.168.111.2
Server IP address: 192.168.111.1
DHCP options:
Message type: DHCPOFFER (2)
lease-time: 86400 ( 1d )
dns-server: 192.168.111.2
dns-server: 192.168.111.1
Your recent debug log shows that your router currently distributes only Pi-hole.
Assuming you've changed that only recently, clients that yet wouldn't have renewed their DHCP lease could still use your router for DNS and thus by-pass Pi-hole (your current lease time is set to one day).
