[Bug 998712] Re: domain name completion broken when dnsmasq is used

[Thomas Hood]

@Wolf: Is it the case that when using the NM-controlled dnsmasq, fully
qualified domain names can always be resolved using the glibc resolver
but short domain names cannot be resolved using the resolver, despite
the correct "search" option being present in /etc/resolv.conf; that this
anomaly does not always occur, but when it does occur it lasts about
five minutes?

Please correct me if any of the following is not (no longer) true.
Please try to provide as complete information as possible.

In the anomalous situation, your /etc/resolv.conf contains the following

    nameserver 127.0.1.1
    search rsb.intern rsb.at

and "nm-tool|grep DNS" shows the following

    DNS:    10.1.0.4

and the following command fails with "unknown host s4"

    ping s4

but the following two commands succeed.

    ping s4.rsb.intern
    ping s4.rsb.at

When the anomaly occurs, does "dig s4.rsb.intern" work on the affected
system?

When the anomaly occurs, does "dig s4.rsb.at" work on the affected
system?

When the anomaly occurs, does "dig s4 +search" work on the affected
system?

-- 
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/998712

Title:
  domain name completion broken when dnsmasq is used

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