But the generated /etc/netplan/50-cloud-init.yaml contains no search domains under nameservers for the interface:
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
enp1s0: addresses:
- 10.48.7.48/21 gateway4: 10.48.0.1
match: macaddress: 52:54:00:9a:b4:64
mtu: 1500 nameservers: addresses:
- 10.48.0.5 set-name: enp1s0
On a MAAS-deployed node, /etc/cloud/ cloud.cfg. d/50-curtin- networking. cfg contains:
network: nameservers: ck.internal
config:
- id: enp1s0
mac_address: 52:54:00:9a:b4:64
mtu: 1500
name: enp1s0
subnets:
- address: 10.48.7.48/21
dns_
- 10.48.0.5
gateway: 10.48.0.1
type: static
type: physical
- address:
- 10.48.0.5
search:
- bos01.canonista
type: nameserver
version: 1
But the generated /etc/netplan/ 50-cloud- init.yaml contains no search domains under nameservers for the interface: cloud.cfg. d/99-disable- network- config. cfg with the following:
addresses:
gateway4: 10.48.0.1
macaddress: 52:54:00:9a:b4:64
nameserver s:
addresses:
set- name: enp1s0
# This file is generated from information provided by
# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/
# network: {config: disabled}
network:
version: 2
ethernets:
enp1s0:
- 10.48.7.48/21
match:
mtu: 1500
- 10.48.0.5