PI works when set to DNS on device, unable to resolve when configured on router

[LibertyBeta]

Please follow the below template, it will help us to help you!

Expected Behaviour:

Setup Pi hole, set static IP for it on a Netgear WNDR3700v4, ads are blocked

Actual Behaviour:

DNS doesn't resolve for any url.

Debug Token:

Can generate if needed.

[jfb]

Please upload a debug log and post the token. Thanks.

[LibertyBeta]

Will do.

Also, I think the issue might be because my home router is its own nat and DCHP. If I don't then I can't change DNS on the ISP supplied router.

Would setting the "router behind router" config in fix this?

[jfb]

@LibertyBeta

I think the issue might be because my home router is its own nat and DCHP. If I don’t then I can’t change DNS on the ISP supplied router.

This may be the case. The also might be a DNS setting buried somewhere in the router setup menus that is letting DNS bypass the Pi-Hole.

For routers where you can't change DNS, use the Pi-Hole DHCP server and turn off this feature in the router.

How do I use Pi-hole's built in DHCP server (and why would I want to)?

Using Your Existing Router For Network-wide Ad Blocking You might not need to use Pi-hole's DHCP server: In many home environments, your router also functions as your DHCP server. In this case, you can often set Pi-hole to be the DNS server for your network clients in the router's DHCP (or LAN) settings page, which allows all of your network clients to block ads simply by connecting to the network. Setting it up this way is also what makes Pi-hole very powerful for network-wide ad blocking. …

[LibertyBeta]

I can set it on my router, but then all devices thing its the DNS(10.0.0.1) vs the Pi(10.0.0.50).

[jfb]

@LibertyBeta

I can set it on my router

You can set what?