Comment 5 for bug 1664806
Revision history for this message
| Ryan Harper (raharper) wrote Re: [Bug 1664806] Re: No documented way to set a default DNS server if no per-interface servers exist | #5 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
On Tue, Mar 21, 2017 at 9:56 AM, Mike Pontillo <email address hidden>
wrote:
> Another note on this: today I'm visiting a customer and the issue of
> "default DNS" came up. The normal use case for MAAS is "everything
> points to the MAAS server", which implies no special DNS setup on a per-
> subnet/
>
> The way this is currently accomplished with curtin is to write the
> default DNS servers into the loopback interface declaration in
> /etc/network/
>
> Is it possible to do something similar with networkd?
>
I'm not sure if it does this natively, a workaround that I'm applying
in cloud-init's rendering of netplan config is to repeat "global" dns config
on each interface.
I'm not sure that cloud-init or curtin (or even netplan) could know if a
global dns route makes "sense" on a particular interface or not; but
maybe at the MAAS level would have enough information.