-
|
The cc pihole integration is my only dns server right now — when I restart containers to do updates pihole goes down and I have to change dns in router back to Google to update, is anyone doing anything clever to avoid this? Only option I’ve thought of so far is second pihole |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
What I use is a quite blunt solution. I changed the DNS settings of the Docker Host, so that it points to my router. You can also use Google here, if that is what you prefer. Setting the DNS server on a Linux hosts, depends on your distro and configuration. So that is up to yourself to check that out. You can also go more advanced by looking into putting a dnsmasq service on your local machine and use that to determine which queries go where (e.g. Local LAN queries to PI-Hole, all else to Router/Google). For my own configuration, this is too complex. Note: When you are using a Linux Distribution as your Docker Host (something I highly recommend), you best handle this as a dedicated server. So no desktop applications on it. This means that there is no need for a PI-Hole, or similar solution, since you wold never use the Docker host itself to browse Internet, and thus get advertisements. |
Beta Was this translation helpful? Give feedback.
What I use is a quite blunt solution. I changed the DNS settings of the Docker Host, so that it points to my router. You can also use Google here, if that is what you prefer.
Setting the DNS server on a Linux hosts, depends on your distro and configuration. So that is up to yourself to check that out.
You can also go more advanced by looking into putting a dnsmasq service on your local machine and use that to determine which queries go where (e.g. Local LAN queries to PI-Hole, all else to Router/Google). For my own configuration, this is too complex.
Note: When you are using a Linux Distribution as your Docker Host (something I highly recommend), you best handle this as a dedicated server…