On 21 October 2017 at 21:51, Steve Langasek
<email address hidden> wrote:
> On Sat, Oct 21, 2017 at 08:54:03AM -0000, diabloneo wrote:
>> No, I wasn't using resolvconf.
>
> Ok, is there any particular reason for that? The resolvconf package is part
> of ubuntu-minimal in Ubuntu 17.04. Removal of ubuntu-minimal leaves you
> with an unsupported configuration.
If you want to switch to the new default configuration you can do this:
And reboot. both ifupdown and network-manager, in 17.10 feed
nameservers to resolved and this is what default configuration should
look like.
Otherwise you need to specify nameserver in either /etc/resolv.conf
direct, or by supplying them to network-manager and asking it to
manage the /etc/resolv.conf.
On 21 October 2017 at 21:51, Steve Langasek
<email address hidden> wrote:
> On Sat, Oct 21, 2017 at 08:54:03AM -0000, diabloneo wrote:
>> No, I wasn't using resolvconf.
>
> Ok, is there any particular reason for that? The resolvconf package is part
> of ubuntu-minimal in Ubuntu 17.04. Removal of ubuntu-minimal leaves you
> with an unsupported configuration.
If you want to switch to the new default configuration you can do this:
$ sudo ln -fs ../run/ systemd/ resolve/ stub-resolv. conf /etc/resolv.conf
And reboot. both ifupdown and network-manager, in 17.10 feed
nameservers to resolved and this is what default configuration should
look like.
Otherwise you need to specify nameserver in either /etc/resolv.conf
direct, or by supplying them to network-manager and asking it to
manage the /etc/resolv.conf.
--
Regards,
Dimitri.