[Dnsmasq-discuss] Simple conf for local hostname resolution only

[Jan Seiffert]

2011/5/18 John Frankish <j-frankish at slb.com>:
[snip]
> ..and herein lies the problem - the dhcp server is a cisco rvs4000 router.
>
> If I understand correctly, there's no way for dnsmasq to get the name/ipaddr pairs and/or
> ipaddr/macaddr pairs from the router and thus it will not be able to resolve the local hostnames?

Not that easy. Maybe there is no way.
See, that's the beauty of dnsmasq, it is all-in-one, so this
dhcp<->dns coupling simply works.
Normally dnsmasq should be the software running on the cisco (and
often is on equip. you buy which does dhcp-dns).

But dnsmasq is no full blown uber dns server, more a simple proxy with
benefits. dnsmasq does not support any fancy update protocols, like
client requests or zone transfers (to keep it small and simple).

You could configure dnsmasq to ask a specific dns server (the cisco?)
for a specific domain (you lan local domain), but i guess that would
fail with non expanded queries (you can configure dnsmasq to expand
queries, but only with the local domain and then they are local, and
dnsmasq does not forward queries deemed as local to anyone).

You could maybe use the cisco as a dhcp relay? The cisco does foo bar
only the cisco can do, but for the final allocation it hands off to
dnsmasq, which then has the full picture and can answer dns queries
about local clients.

If all else fails, maybe you can copy some kind of database with the
allocations from the cisco so it can be spoon feed into dnsmasq.

Are the clients behind the cisco? Otherwise take the cisco out of the
picture, disable it's dhcp server.

Greetings
Jan