This shows you the differences between two versions of the page.
Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
userdoc:guest_lxc_container_pihole [2020/06/07 08:13] abelbeck |
userdoc:guest_lxc_container_pihole [2022/01/07 09:47] abelbeck |
**Override default DHCP dns-server option** | **Override default DHCP dns-server option** |
| |
By default, dnsmasq offers the ''dns-server'' IP address using the gateway address for that subnet. In the case when you want all clients in a subnet to use the Pi-hole server you can override the default settings by editing your ''/mnt/kd/dnsmasq.static'' file with the following: | By default, the DHCP server (dnsmasq) offers the ''dns-server'' IP address using the gateway address for that subnet. With Pi-hole you may want all DHCP clients in a subnet to use the Pi-hole server for DNS. You can override the default settings by editing your ''/mnt/kd/dnsmasq.static'' file with the following: |
| |
## Override default dns-server option | ## Override default dns-server option |
#dhcp-option=dmz,option:dns-server,192.168.200.10 | #dhcp-option=dmz,option:dns-server,192.168.200.10 |
| |
Replace the ''192.168.200.10'' IP address with your Pi-hole server's static address and uncommnet for each subnet you want it to apply. In the web interface, select "Restart DNS & DHCP" to apply the change to the dnsmasq configuration. | Replace the ''192.168.200.10'' IP address with your Pi-hole server's static address and uncomment for each subnet you want it to apply. In the web interface, select "Restart DNS & DHCP" to apply the change to the dnsmasq configuration. |
| |
| \\ |
| **Pi-hole Interface Settings Config** |
| |
| Newer versions of Pi-hole default to "Interface Settings" set to "Allow only local requests", which does not work on a LXC container with an interface attached to an internal AstLinux ''lxcbr0'' bridge. You will know this is an issue when no DNS is received and Pi-hole dnsmasq logs "Ignoring query from non-local network". |
| |
| One solution is to change the Pi-hole Interface Setting from "Allow only local requests" to "Respond only on interface ...". |
| |