> 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
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
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:
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
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
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
6 matches
Mail list logo