Pi-hole's DHCP service should announce different DNS to clients

[jfb]

@74cmonty

Expected Behaviour:

Pi-hole’s DHCP service must announce different DNS server to clients

This is not the expected behavior. The expected behavior is that Pi-Hole provides itself as DHCP to clients, so they will route DNS through Pi-Hole.

There is a method to use an alternate DNS for individual clients, but this is not the default Pi-Hole behavior.

To do this, Pi-Hole must be the DHCP server. These thread provide guidance.

Secondary DNS Server for DHCP

Sure. So the dhcp-option=6,Pi-holeIP,SecondaryDNSIP Woyld look like this: dhcp-option=6,192.168.1.2,8.8.8.8 Assuming pi has 192.168.1.2 ip. Replace with what you have. 8.8.8.8 is the google dns So if you use your pi as dhcp server, it will push those ips as primary and secondary ips.

Things you can do with dnsmasq!

I came up with some stuff that eases things a little bit with my Pi-Hole life. Some of the ideas here, I gathered from around the internet. I wanted to share my findings. These configs are to be placed in /etc/dnsmasq.d I do realize that these could easily be combined into a single 04-custom.conf, but for the ease of teaching myself things I can do with this,, I like them seperate. Bypass Pihole by MAC Address What this Does: Find the MAC Address of the device that you want to skip pihole, …