Comment 6 for bug 1786726

Verification done on bionic with netplan.io

I was able to confirm that in an IPv6-only scenario, netplan now does not render invalid dns-search for the IPv4 method.

root@working-guinea:~# cat /run/NetworkManager/system-connections/netplan-eth0
[connection]
id=netplan-eth0
type=ethernet
interface-name=eth0

[ethernet]
wake-on-lan=0

[ipv4]
method=link-local

[ipv6]
method=manual
address1=23:b0:87:58:65:f7:fb:8b/45
address2=63:94:73:e1:46:15:79:58/50
dns=f2:9d:bc:04:7b:87:ec:28;
dns-search=lab;home;
root@working-guinea:~# nmcli con
NAME UUID TYPE DEVICE
netplan-eth0 04d79829-8fbf-3091-8dac-4378e0daab6d ethernet eth0
root@working-guinea:~# nmcli con show id netplan-eth0 | grep ipv4
ipv4.method: link-local
ipv4.dns: --
ipv4.dns-search: --
ipv4.dns-options: ""
ipv4.dns-priority: 0
ipv4.addresses: --
ipv4.gateway: --
ipv4.routes: --
ipv4.route-metric: -1
ipv4.route-table: 0 (unspec)
ipv4.ignore-auto-routes: no
ipv4.ignore-auto-dns: no
ipv4.dhcp-client-id: --
ipv4.dhcp-timeout: 0 (default)
ipv4.dhcp-send-hostname: yes
ipv4.dhcp-hostname: --
ipv4.dhcp-fqdn: --
ipv4.never-default: no
ipv4.may-fail: yes
ipv4.dad-timeout: -1 (default)