Hi On 8/25/24 12:07 PM, Danil Smirnov wrote:
> There is some evidence on the Internet that dnsmasq doesn't play well > with Docker (when run in a Docker container), i.e.: > https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2021q4/015909.html That says: > This software will then send the HUP signal to dnsmasq when the > config files change. I know that the author doesn't mention any issues reloading the configuration file but I think it's worth noting that this is not what the HUP signal does to dnsmasq. I made the same mistake previously in my own script and in actuality this is what it does per the man page: > When it receives a SIGHUP, dnsmasq clears its cache and then > re-loads /etc/hosts and /etc/ethers and any file given by > --dhcp-hostsfile, --dhcp-hostsdir, --dhcp-optsfile, --dhcp- > optsdir, --addn-hosts or --hostsdir. The DHCP lease change > script is called for all existing DHCP leases. If --no-poll > is set SIGHUP also re-reads /etc/resolv.conf. SIGHUP does > NOT re-read the configuration file. _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
