Comment 24 for bug 1750884
Revision history for this message
| Scott Moser (smoser) wrote Re: [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution | #24 |
I'm pretty sure that if you you rm /etc/resolv.conf
and then just write what ever you want in there, it wont get overritten.
mv /etc/resolv.conf /etc/resolv.
echo "nameserver 8.8.8.8" > /etc/resolv.conf
On Thu, Mar 8, 2018 at 4:36 PM, Mike Pontillo <email address hidden>
wrote:
> We discussed this today and decided that the proper place to fix this is
> not in MAAS; the v1 YAML containing global DNS servers should be
> converted to equivalent valid Netplan (using a heuristic).
>
> Alternatively, global DNS could be added to the Netplan schema (possibly
> as a shortcut to apply configuration to a group of interfaces).
>
> --
> You received this bug notification because you are a member of Canonical
> Cloudware, which is subscribed to cloud-init.
> Matching subscriptions: cloud-init bugs
> https:/
>
> Title:
> [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
> leads to no DNS resolution
>
> To manage notifications about this bug go to:
> https:/
>