Hey all,
Is anyone else having problems with DNS resolution after upgrading to
Ubuntu GNOME Yakkety?
/etc/resolv.conf points to 127.0.0.1 as if dnsmasq is still being used,
but nothing is listening on that, while systemd-resolved is running and
listening on 127.0.0.53 instead.
The dnsmasq
Did you check if you're connected to your network ?
May be it's a problem with the network driver that doesn't resume ?
2016-10-06 21:39 GMT-04:00 Michael Gratton :
>
> Hey all,
>
> Is anyone else having problems with DNS resolution after upgrading to
> Ubuntu GNOME Yakkety?
>
> /etc/resolv.conf
No, the connection is there. I can ping IP addresses.
--
Sent from my outboard brain.
On 7 October 2016 12:49:12 PM Bernard Tremblay
wrote:
Did you check if you're connected to your network ?
May be it's a problem with the network driver that doesn't resume ?
2016-10-06 21:39 GMT-04:00 M
I believe resolved conflicts with dnsmasq.
Sent from my iPhone
> On Oct 6, 2016, at 7:21 PM, Michael Gratton wrote:
>
> No, the connection is there. I can ping IP addresses.
>
> --
> Sent from my outboard brain.
>> On 7 October 2016 12:49:12 PM Bernard Tremblay
>> wrote:
>>
>> Did you che
On Fri, Oct 7, 2016 at 2:01 PM, Herminio Hernandez Jr.
wrote:
I believe resolved conflicts with dnsmasq.
It doesn't actually seem to.
In any case, "only" dnsmasq-base is installed, since both
network-manager (and lxc1) still depend on it, however dnsmasq
instances are still being launched b
