Pihole DHCP with Verizon G3100

Hey everyone - I've been trying to find a conclusive answer to this and was wondering if anyone could help. I'm running pihole on a Raspberry Pi 3B and I'm on Verizon with the G3100. I'd like to use pihole for my DHCP because I like having the device and traffic info tied together. I've got the DNS setup working fine, but am at a loss for how to properly configure the G3100 if I want to use pihole for DHCP. I know I'd have to enable DHCP on the pihole. Also, I'm not trying to eliminate my G3100. Also, I don't have any other Verizon services to worry about—I'm strictly just an Internet customer.

Does anyone have experience with this that could float me some screenshots or some steps on what to do? Thanks much!

(Internet Protocol; Bridge - Verizon Wireless G3100 User Manual [Page 64] | ManualsLib)

As I said before: you are in the woods.

Assume you've set up unbound and set pi-hole setting DNS/Upstream DNS Servers/Custom 1/ to 127.0.0.1#5335 and disabled other DNS servers

From admin login on Quantum G3100 (192.168.1.1 typ. and pw on router)

  1. My Network/Network Connections/Broadband Connection/Settings/IPv4 DNS/No IPv4 DNS #prevents G3100 from "helping" with DNS

  2. Advanced/IPv4 Address Resolution - Network(Home/Office) Disabled #takes out second DNS server

  3. Advanced/DNS Server/Add DNS Entry [Host Name pi-hole (name not important) and static IP address of your pi-hole, e.g., 192.168.1.2 ] #probably a reason for this that escapes me, like prevent conflict with pi-hole DNS DHCP

Good luck!

1 Like

Thank you for showing how deep they are into the woods.

It looks like they will break everything trying that all.

It works just fine. Only "issue" is regular dnsmasq warnings for an interface which has no address (due to use of PPPoE on broadband?).

Oh, I'm sure it works...

But do they seem like they can implement it?

FTR: I use the most secure setting "only allow local requests" and it shows up a couple times a week.
If I may ask: do you use the Pi for DHCP and why?

If I recall, it was because the Quantum DHCP demanded two DNS addresses, which breaks the blocking if you use pi-hole IP for first and a public DNS for the second. Also I wanted to experiment with pi-hole's DHCP for a larger network where we had been using the less than robust DHCP on Cisco's 5500 series firewall.

1 Like

Oh, you are cooperate.

That makes sense.

Thank you!

Thanks so much! That totally worked. I actually hadn't set up Unbound but got that up and running then followed your instructions and it worked like a charm. Much appreciated!

1 Like

I regret underestimating you.

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.