Am 08.02.2017 um 02:59 schrieb Josh Triplett:
> On Tue, Feb 07, 2017 at 11:22:19PM +0100, Michael Biebl wrote:
>> Am 06.02.2017 um 10:14 schrieb Tilo Villwock:
>>> Package: network-manager
>>> Version: 1.6.0-1
>>> Severity: important
>>> Tags: upstream
>>>
>>> Dear Maintainer,
>>>
>>> resolving of hostnames stopped working after updating the package and as it
>>> turns out the search domain string is being duplicated in resolv.conf (e.g.
>>> 'search domain.orgdomain.org'). Right now I have to configure the connection
>>> manually to resolve this.
>>
>> I can't reproduce the problem.
>> I tried both the internal dhcp implementation and isc-dhcp-client (4.3.5-3).
>>
>> Josh, since you raised the severity, I assume you can reproduce the problem?
>
> Yes, I have the same issue here at work ("search
> jf.intel.comjf.intel.com"), and I can reliably reproduce it.
>
>> Would be great to have more information on how to reproduce the problem.
>
> I have isc-dhcp-client 4.3.5-3, and network-manager 1.6.0-1. Happy to
> provide additional information.
>
> Have you tested on a network configured to hand out a search domain?
> Does the search domain include multiple components as "domain.org" and
> "jf.intel.com" do?Works fine here: This is from my dnsmasq.conf: dhcp-range=192.168.179.50,192.168.179.150,12h dhcp-option=option:domain-search,test.example.com,foo.com The resulting /etc/resolv.conf # Generated by NetworkManager search test.example.com foo.com nameserver 192.168.179.10 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
