Hello, Tony, thanks for reaching out and reporting your issue.
From `netplan set --help`:
---
$ netplan set --help
usage: /usr/sbin/netplan set [-h] [--debug] [--origin-hint ORIGIN_HINT]
[--root-dir ROOT_DIR] key_value
Add new setting by specifying a dotted key=value pair like
ethernets.eth0.dhcp4=true
positional arguments:
key_value The nested key=value pair in dotted format. Value can
be NULL to delete a key.
---
That means setting a new value will add it to the existing value list.
If you want to clear the list of nameservers and then add yours, you can
do
# netplan set "ethernets.eth0.nameservers.addresses=NULL"
and then
# netplan set "ethernets.eth0.nameservers.addresses=[192.168.100.1,
192.168.100.19]"
As this is expected behavior, I am closing this bug as invalid (not a bug).
If you have any other concern or you believe there is indeed a bug on how
`netplan set` works, feel free to reopen.
** Changed in: netplan.io (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2116180
Title:
Using "netplan set" to update nameservers not as expected
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/2116180/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
