[Dnsmasq-discuss] [PATCH] --dont-mirror-queries option

[Chris Novakovic]

On 13/02/2016 13:09, Simon Kelley wrote:
> Will try and remember to reply to your other points, but on this one,
> the way I'd do it (assuming you don't have problems with slow or
> intermittent connectivity) is to have one (primary) dnsmasq which is the
> DHCP server for all three networks. You declare all the address ranges
> in the config of the primary, and tell the secondaries to do dhcp-relay
> to the primary.
> 
> That keeps all the DHCP address information in the primary, so as long
> as the secondaries forward to the primary, all names should be resolvable.

Ideally this is what I would have done, but the three sites (which each
use their own /26 subnet inside a common /24) are geographically
distant, connected to each other via a layer-3 VPN over somewhat
unreliable links --- this means that each site really has to have an
authoritative DHCP server for its own /26 subnet, and the only thing
suitable for splitting across all three sites is DNS service (that way,
if area1 gets cut off from the rest of the /24, area1's dnsmasq can
still assign DHCP leases for its own /26, and it doesn't matter that it
can't resolve a name that's active on area2 because it wouldn't be able
to communicate with that host anyway).

Cheers,
Chris