Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
Thanks for testing Am 14.02.2017 um 10:50 schrieb Tilo Villwock: > I only installed the newly created network-manager_1.6.0 package > though. When this is fixed and a new version gets into the > repositories. Will my own package be removed automatically in favor of > the new one? If you didn't change the version number and kept 1.6.0-1 it will be upgraded automatically. -- 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
Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
> Would be great if you can test with this patch applied and report > back. So this fixed the problem for me. I patched the source tarball I got from apt source and created a new package with: dpkg-buildpackage -rfakeroot -uc -b I only installed the newly created network-manager_1.6.0 package though. When this is fixed and a new version gets into the repositories. Will my own package be removed automatically in favor of the new one? Thanks --Tilo
Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
The patch you mention fixed the behavior for me. Thx, Martin On 02/13/2017 10:28 PM, Michael Biebl wrote: Am 10.02.2017 um 09:49 schrieb Tilo Villwock: Bug report filed: https://bugzilla.gnome.org/show_bug.cgi?id=778430 Upstream provided a patch at https://bugzilla.gnome.org/show_bug.cgi?id=778430#c10 Would be great if you can test with this patch applied and report back. Regards, Michael
Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
Am 10.02.2017 um 09:49 schrieb Tilo Villwock: > > Bug report filed: > > https://bugzilla.gnome.org/show_bug.cgi?id=778430 Upstream provided a patch at https://bugzilla.gnome.org/show_bug.cgi?id=778430#c10 Would be great if you can test with this patch applied and report back. Regards, Michael -- 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
Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
On 10/02/17 03:00, Michael Biebl wrote: > On Thu, 9 Feb 2017 11:31:19 +0100 =?UTF-8?Q?Martin_Haa=c3=9f?= > wrote: >> Same behavior happens here. >> Is it possible that multiple search domain entries in the dhcp packet >> trigger this problem? So instead of one entry being written twice it is >> two entries being concatenated without a newline and an additional >> 'search' keyword at the start of the line. >> >> Following is a wireshark trace of our DHCP ACK. There are two search >> domain entries (Option 3) due to two name server entries. > >> Option: (15) Domain Name >> Length: 11 >> Domain Name: company.local > >> Option: (15) Domain Name >> Length: 11 >> Domain Name: company.local > > Have you configured 2 identical search domains or is the dhcp server > doing something odd? > AFAIK its two identical search domains. Should be a Microsoft DHCP server serving two DNS entries each configured with address and default search domain
Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
> Tilo, Josh, since you are able to reproduce the issue and I'm not, > could > any of you file this issue upstream at > https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager > and report back with the bug number. > > Thanks, > Michael > Bug report filed: https://bugzilla.gnome.org/show_bug.cgi?id=778430 --Tilo
Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
On Mon, 06 Feb 2017 10:14:46 +0100 Tilo Villwock wrote: > 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. Tilo, Josh, since you are able to reproduce the issue and I'm not, could any of you file this issue upstream at https://bugzilla.gnome.org/enter_bug.cgi?product=NetworkManager and report back with the bug number. Thanks, Michael -- 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
Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
On Thu, 9 Feb 2017 11:31:19 +0100 =?UTF-8?Q?Martin_Haa=c3=9f?= wrote: > Same behavior happens here. > Is it possible that multiple search domain entries in the dhcp packet > trigger this problem? So instead of one entry being written twice it is > two entries being concatenated without a newline and an additional > 'search' keyword at the start of the line. > > Following is a wireshark trace of our DHCP ACK. There are two search > domain entries (Option 3) due to two name server entries. > Option: (15) Domain Name > Length: 11 > Domain Name: company.local > Option: (15) Domain Name > Length: 11 > Domain Name: company.local Have you configured 2 identical search domains or is the dhcp server doing something odd? -- 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
Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
Same behavior happens here. Is it possible that multiple search domain entries in the dhcp packet trigger this problem? So instead of one entry being written twice it is two entries being concatenated without a newline and an additional 'search' keyword at the start of the line. Following is a wireshark trace of our DHCP ACK. There are two search domain entries (Option 3) due to two name server entries. Cheers, Martin snip Bootstrap Protocol (ACK) Message type: Boot Reply (2) Hardware type: Ethernet (0x01) Hardware address length: 6 Hops: 0 Transaction ID: 0x34e7e163 Seconds elapsed: 0 Bootp flags: 0x (Unicast) Client IP address: 0.0.0.0 Your (client) IP address: 192.168.0.43 Next server IP address: 10.49.24.25 Relay agent IP address: 0.0.0.0 Client MAC address: Dell_50:03:a7 Client hardware address padding: Server host name not given Boot file name: netboot/lpxelinux.0 Magic cookie: DHCP Option: (53) DHCP Message Type (ACK) Option: (58) Renewal Time Value Option: (59) Rebinding Time Value Option: (51) IP Address Lease Time Option: (54) DHCP Server Identifier Option: (1) Subnet Mask Option: (28) Broadcast Address Option: (3) Router Length: 4 Router: 192.168.0.6 Option: (15) Domain Name Length: 11 Domain Name: company.local Option: (6) Domain Name Server Option: (28) Broadcast Address Option: (3) Router Length: 4 Router: 192.168.0.6 Option: (15) Domain Name Length: 11 Domain Name: company.local Option: (6) Domain Name Server Option: (44) NetBIOS over TCP/IP Name Server Option: (42) Network Time Protocol Servers Option: (252) Private/Proxy autodiscovery Option: (255) End -- snap -
Bug#854343: [Pkg-utopia-maintainers] Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
> So, interestingly, I can reliably reproduce this on my work network, > but > not on VPN (which also provides a search domain, albeit a different > one). I can confirm this. When I connect to a VPN the domain entries are handled correctly. Both the local and the remote domains are configured properly. --Tilo
Bug#854343: [Pkg-utopia-maintainers] Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
Am 08.02.2017 um 05:33 schrieb Josh Triplett: > So, interestingly, I can reliably reproduce this on my work network, but > not on VPN (which also provides a search domain, albeit a different > one). > > Also, can you test with just a single domain-search rather than two? Tried both, doesn't make a difference. -- 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
Bug#854343: [Pkg-utopia-maintainers] Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
On Wed, Feb 08, 2017 at 05:15:56AM +0100, Michael Biebl wrote:
> 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
So, interestingly, I can reliably reproduce this on my work network, but
not on VPN (which also provides a search domain, albeit a different
one).
Also, can you test with just a single domain-search rather than two?
- Josh Triplett
Bug#854343: [Pkg-utopia-maintainers] Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
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
Bug#854343: [Pkg-utopia-maintainers] Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
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?
- Josh Triplett
Bug#854343: [Pkg-utopia-maintainers] Bug#854343: network-manager: The search domain string in resolv.conf is being duplicated leading to problems with DNS
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? Would be great to have more information on how to reproduce the problem. Michael -- 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
