[Dnsmasq-discuss] Restrict nameserver interfaces but not dhcp ones
Luigi Baldoni
aloisio at gmx.com
Fri Jan 5 08:58:19 UTC 2024
On 4 January 2024, Geert Stappers wrote:
> > On Thu, Jan 04, 2024 at 08:08:46PM +0100, Luigi Baldoni wrote:
> >
> > I'm trying to get rid of a second (kea) dhcp server and
> > hopefully be able to do everything I need with dnsmasq.
> >
> > The main hurdle, so far, is to run the nameserver only
> > on eth1, because bind is listening on eth0, but have
> > the dhcp server listen on both interfaces (and more).
>
> What has already been tried?
Done several tests and if I launch dnsmasq first then neither it nor bind will complain,
but ss lists both listening on port 53 on the same interface.
> Advice: Tell in the reply more about the network, such as
> which IP-addresses are on the network interfaces.
This is a map of my network:
lan15 192.168.7.0/24 bind on 192.168.7.100 and dnsmasq dhcp on the same address (can be changed)
lan30 192.168.8.0/24 dnsmasq dhcp on 192.168.8.150
lan45 192.168.11.0.24/ dnsmasq dhcp on 192.168.11.150
lan130 192.168.130.0/24 dnsmasq ns and dnsmasq dhcp on 192.168.130.200
lan166 192.168.166.0/24 dnsmasq dhcp on 192.168.166.200
Regards
More information about the Dnsmasq-discuss
mailing list