Re: [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2013-02-04 Thread Sergio Callegari
On 04/02/2013 15:40, Simon Kelley wrote: On 03/02/13 07:48, Thomas Hood wrote: there's still the unresolved question of whether re-enabling --strict-order will suffice as a workaround, since 12.10 relies on DBus to populate the nameservers. Is there any extra information on this? Please

Re: [Bug 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

2013-02-04 Thread Sergio Callegari
On 04/02/2013 17:07, Simon Kelley wrote: On 04/02/13 15:36, Sergio Callegari wrote: On 04/02/2013 15:40, Simon Kelley wrote: On 03/02/13 07:48, Thomas Hood wrote: there's still the unresolved question of whether re-enabling --strict-order will suffice as a workaround, since 12.10 relies

[Bug 993794] Re: Precise resolvconf+dnsmasq setup breaks login in some wireless networks

2012-05-08 Thread Sergio Callegari
No, unfortunately, I do not think it is that. If I start with my machine OFF, I switch it on and boot, then I already have the issue. The machine connects to the wifi, but when I open the browser I cannot reach the authentication screen because the name of the authentication host cannot be

[Bug 993794] Re: Precise resolvconf+dnsmasq setup breaks login in some wireless networks

2012-05-07 Thread Sergio Callegari
Let me add that the /var/run/nm-dns-dnsmasq.conf contains 3 servers set by nm on activation of the wireless interface and received via dhcp. The first one is internal. The other ones are external. -- You received this bug notification because you are a member of Ubuntu Server Team, which is

[Bug 993794] Re: Precise resolvconf+dnsmasq setup breaks login in some wireless networks

2012-05-03 Thread Sergio Callegari
** Summary changed: - Precise resolvconf+dnsmasq setup breaks logging in some wireless networks + Precise resolvconf+dnsmasq setup breaks login in some wireless networks -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in