[Dnsmasq-discuss] domain per interface
rob0 at gmx.co.uk
Wed Mar 19 01:54:24 GMT 2008
On Tue March 18 2008 18:42:44 richardvoigt at gmail.com wrote:
> If all else fails, you can run two instances of dnsmasq with two
> separate config files, each bound to a different interface.
Indeed, but that's something I would like to avoid. Here's what I
> > dnsmasq.conf :
> > ...
> > dhcp-range=wifi,192.168.3.127,192.168.3.192,255.255.255.0,12h
> > dhcp-option=wifi,15,wifi.example.net
> > ...
> > (where 192.168.3.1 is the wireless interface IP address)
But that only works for the domain pushed to clients, not for the
domain used by dnsmasq for forward/reverse DNS names of clients. I get
"search wifi.example.net" in their resolver files, but that's rather
useless, since no names have ".wifi.example.net." in them.
I think that in ISC dhcpd/named, this could be done with a subnet
declaration block with "option domain-name wifi.example.net;" inside
it, and of course a corresponding dynamic zone declaration in
named.conf. That's another avenue I don't want to pursue, because I
want to keep dnsmasq for authoritative DNS. (I'm using named for
recursion only, on port 35, with dnsmasq using "server=127.0.0.1#35".)
Simon, am I out of luck here?
I guess I could also do dhcp-script and nsupdate(8) to update a zone
in named.conf. But even then, will the dnsmasq block it? If dnsmasq
knows the answer, named is never consulted. What about this:
Will dnsmasq ignore the names it has served to DHCP clients?
Offlist mail to this address is discarded unless
"/dev/rob0" or "not-spam" is in Subject: header
More information about the Dnsmasq-discuss