My Emailiases: [Dnsmasq-discuss] multiple domain support - question

L Forrister e1-7n32-h2qw-w2h3 at snugmail.com
Mon Aug 4 18:46:12 BST 2008


Simon Kelley (simon at thekelleys.org.uk) (Emailias: REPLY-MASKED) wrote:
> Original Sender:  <dnsmasq-discuss-bounces at lists.thekelleys.org.uk>
> Given To:  lists.thekelleys.org.uk: Dnsmasq-discuss Info Page
> http://www.emailias.com/mailclick/?id=243457
> <--------------------end emailias header-------------------->
>
> I have support for multiple domains working, but I've come across a wrinkle.
>
> Consider the case that two different DHCP clients claim the same name.
> With the existing code, only one can have it and the current behaviour
> is that when a second machine  claims a name, the first one loses it.
>
> Now, consider the possibility that the two machines claiming the same
> name are in different domains. By default, the existing behaviour must
> continue, because the unqualified name is added to the DNS, so that even
> though the two clients could have "name.domain1.com" and
> "name.domain2.com", they are still fighting over just plain "name".
>
> It would be possible to introduce a new mode, which didn't put the
> unqualified name into the DNS, and allowed both hosts to keep their name
> as long as they are in different domains. Would that be useful, or just
> an confusing complication?
>
>
>   

I don't see anything confusing about it.  What good is multiple domain
support if you're forced to maintain unique host names across all domains.


I've never quite understood why dnsmasq can't allow the duplicate names
in the first place.  Why must it be so.  Consider a client machine with 
two interfaces.  Both dhcp.  They'll both get leases.  Both ip's will be 
active.  But the dns will only return one (name and ip) depending on 
which was most recently renewed.  But its not just the dns, because when 
you check the leases file there's only one lease listed.

~~L.Forrister





More information about the Dnsmasq-discuss mailing list