You can run two instances of dnsmasq, each with a different interface it listens on. You can use the –interface=X and –bind-interfaces options for that. By default, it also binds the loopback device lo and will fail if two processes try to bind it. Use –except-interface=lo to avoid that. dnsmasq –interface=eth0 –except-interface=lo –bind-interfaces –dhcp-range=192.168.0.2,192.168.0.10,12h dnsmasq … Read more
A clean solution is to configure docker+dnsmasq so than DNS requests from the docker container are forwarded to the dnsmasq daemon running on the host. For that, you need to configure dnsmasq to listen to the network interface used by docker, by adding a file /etc/NetworkManager/dnsmasq.d/docker-bridge.conf: $ cat /etc/NetworkManager/dnsmasq.d/docker-bridge.conf listen-address=172.17.0.1 Then restart network manager to … Read more
Docker populates /etc/resolv.conf by copying the host’s /etc/resolv.conf, and filtering out any local nameservers such as 127.0.1.1. If there are no nameservers left after that, Docker will add Google’s public DNS servers (8.8.8.8 and 8.8.4.4). According to the Docker documentation: Note: If you need access to a host’s localhost resolver, you must modify your DNS … Read more
In the dnsmasq.conf file, add the line address=/.domain.tld/192.168.0.1 But use the IP you actually want as that end bit