This changes the DNS server upstream of your router. This will work, but is not as good as being able to set the DHCP delivered DNS server. The difference is, with the first option, all your DNS requests are first send from your clients to your router and then to your pihole. For your pihole it looks like all requests are coming from your router and you loose the ability to configure blocking for individual clients. If your clients would send their requests directly to pihole (easiest way is via DHCP), you would get individual stats and the configuration ability.
Another method would be to set the DNS server on each client manually.
I actually disabled both DHCP and DNS on the Verizon router and used Pi-hole for both.
Makes it easier since the entire solution is now handled by Pi-hole.
I found the DHCP setting buried a mile down in my router settings and disabled it. So now Pi-Hole is managing my DHCP, this works as expected however ads are still not being blocked on any of my devices This is perplexing! See log below, please help
Blockquote
It would seem it's only the E3200 that needs the extended DHCP answer, requiring a custom dnsmasq config for Pi-hole to accept it as one of its kind.
That's correct, I was able to disable DHCP on the verizon router and enable it on Pi-Hole but ads are still not being blocked. DHCP doesn't seem to be the issue
Did you reconnect all your clients once from the network to make sure they pickup the new DHCP information, including the DNS server?
From your debug log, is seems some devices have started using pihole
[2020-10-08 03:39:44.065 19592M] -> Total DNS queries: 29255
[2020-10-08 03:39:44.065 19592M] -> Cached DNS queries: 1943
[2020-10-08 03:39:44.065 19592M] -> Forwarded DNS queries: 20261
[2020-10-08 03:39:44.065 19592M] -> Blocked DNS queries: 7051
[2020-10-08 03:39:44.065 19592M] -> Unknown DNS queries: 0
[2020-10-08 03:39:44.066 19592M] -> Unique domains: 1655
[2020-10-08 03:39:44.066 19592M] -> Unique clients: 4
[2020-10-08 03:39:44.066 19592M] -> Known forward destinations: 2
At least your router has started using pihole
query[A] api.us-east-1.aiv-delivery.net from 192.168.1.1
Oct 8 00:00:40 dnsmasq[1712]: forwarded api.us-east-1.aiv-delivery.net to 208.67.220.220
Oct 8 00:00:40 dnsmasq[1712]: query[A] api.us-east-1.aiv-delivery.net from 192.168.1.1
Oct 8 00:00:40 dnsmasq[1712]: forwarded api.us-east-1.aiv-delivery.net to 8.8.8.8
Oct 8 00:00:40 dnsmasq[1712]: forwarded api.us-east-1.aiv-delivery.net to 208.67.220.220
Oct 8 00:00:40 dnsmasq[1712]: reply api.us-east-1.aiv-delivery.net is 54.85.188.39
Your debug log shows they are. The empty boxes on the web admin dashboard are frequently due to a browser ad blocker. If you have these in operation, disable them for the dashboard.
Your debug log shows they are. The empty boxes on the web admin dashboard are frequently due to a browser ad blocker. If you have these in operation, disable them for the dashboard.
I tested adblock using canyoublockit.com and all the ads appeared on my wifi clients and wired desktop. However I did notice a few less ads on my desktop. Have ads just gotten smarter than the pi-hole over the past few months?
The point I am addressing is the incorrect information on your dashboard. The debug log shows Blocked DNS queries: 7051 , but the dashboard does not show this. The blank lines for queries blocked and percent blocked are most commonly caused by an adblocker on the browser preventing these boxes from loading.
Turning off the adblocker for the Pi-hole web admin page typically fixes this problem.
My wired clients are blocking some ads, they pass the canyoublockit simple test, fail the extreme test miserably. My wireless clients are not blocking any ads. Very strange...
You're right, sorry disabling brave browser blocking allows Pi-hole to show my stats. I can confirm ty wired clients are blocking some ads, they pass the canyoublockit simple test, fail the extreme test miserably. My wireless clients are not blocking any ads. Very strange...
Regardless of what you see on the website you are using to test ad blocking, are you seeing actual ads on the wired clients? From what I can see, that testing website is pretty crappy.
As far as I can tell my wireless clients aren't using pi-hole, there is no record of them in the log despite switching to pi-hole as my DHCP server. Any advice?
That screenshot looks like the Termux app for Android ?
My experience is that you cant use nslookup to determine configured DNS servers for Android as it seems the Termux shell always uses 8.8.8.8 regardless of DNS servers configured/received via DHCP.
Better install a network info app that will show the DNS server(s).
This is perplexing! See log below, please help 
