Comment 1 for bug 1818139
Revision history for this message
| Mathieu Trudel-Lapierre (cyphermox) wrote | #1 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
Netplan does not work that way. To configure custom DNS for an interface, you should include all the other features for that device as well.
In other words, this requires also configuring dhcp4: yes, or otherwise setting a static IP address. Only 'nameservers' is not sufficient. If you want to change just the nameservers in use, you can change those directly in the parameters for the interface as well, using the NetwrokManager configuration dialogs.
The message "DEBUG:enp3s0 not found in {}" is not an indication of any bug; it is only debug information for netplan developers to understand how the configuration is parsed, and how it gets to some of the later behavior (such as renaming interfaces, etc.).