[Bug 781557] [NEW] multiple search domains not honoured

[Simon Kelley]

Launchpad Bug Tracker wrote:
> You have been subscribed to a public bug:
> 
> Binary package hint: resolvconf
> 
> in /etc/resolvconf/resolv.conf.d/base I have
> 
> search domain1.local domain2.local
> 
> When trying to connect to a host in domain2.local using only the
> hostname, only the first domain is searched by my local dnscache
> (dnsmasq):
> 
> lieven at T500:~$ ping host2
> ping: unknown host host2
> 
> while dnsmasq only gets the query for domain1.local
> 
> May 12 09:33:38 T500 dnsmasq[4302]: query[A] host2.domain1.local from 127.0.0.1
> May 12 09:33:38 T500 dnsmasq[4302]: forwarded host2.domain1.local to 192.168.5.254
> May 12 09:33:43 T500 dnsmasq[4302]: query[A] host2.domain1.local from 127.0.0.1
> May 12 09:33:43 T500 dnsmasq[4302]: forwarded host2.domain1.local to 192.168.5.254
> 
> my /etc/resolv.conf (linked to /etc/resolvconf/run/resolv.conf) contains
> 
> # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
> #     DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
> nameserver 127.0.0.1
> search domain1.local domain2.local dhcp.supplied.domain.net
> 

Sorry to bounce responsibilty again, but this isn't a dnsmasq problem,
the search-domain function is implemented by the libc resolver code,
which should generate separate DNS queries for host2.domain1.local,
host2.domain2.local, etc. Dnsmasq's only role in this is to forward
those queries. Since from the log, the  host2.domain2.local aren't
getting to dnsmasq, the problem must lie elsewhere.


Cheers,

Simon.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/781557

Title:
  multiple search domains not honoured

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/781557/+subscriptions