A question that crops up regularly on #docker is “How do I attach a container directly to my local network?” One possible answer to that question is the macvlan network type, which lets you create “clones” of a physical interface on your host and use that to attach containers directly to your local network. For the most part it works great, but it does come with some minor caveats and limitations.
To force piHole to push a defined IP address as DNS server to DHCP clients:
-
Edit
/etc/dnsmasq.d/02-pihole-dhcp.conffile:
#> sudo nano /etc/dnsmasq.d/02-pihole-dhcp.conf -
Add the IP address to be push as DNS server:
dhcp-option=6,<Pi-holeIP>,<SecondaryDNSServerIP> -
Save file modification.
-
Restart pihole-FTL server:
sudo service pihole-FTL restart
⚠️ You would have to release/renew DHCP lease on each host after that to pull the new settings.
⚠️ Change is not persistant over time as this file can be overwritten by piHole.
Learn how it is possible to completely disable the Wi-Fi module on your Raspberry Pi by following some straightforward steps.
TL;DR
-
Disable:
sudo rfkill block wifi -
Enable:
sudo rfkill unblock wifi
Tutorials:
- Pi-hole failover using Gravity Sync and Keepalived (davidshomelab.com)
- HA piHole setup with unbound/keepalived/gravitysync (piHole discourse forum)
Tools:
Others:
Official Pi-hole docker image along with DoH (DNS over HTTPS) powered by Cloudflare. - GitHub - eltonk/pihole-doh: Official Pi-hole docker image along with DoH (DNS over HTTPS) powered by Cloudflare.