yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <2004131@xxxxxxxxxxxxxxxxxx>]

[Expired for cloud-init because there has been no activity for 60 days.]

** Changed in: cloud-init
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to cloud-init.
https://bugs.launchpad.net/bugs/2004131

Title:
  cloud-init doesn't set dns search domains

Status in cloud-init:
  Expired

Bug description:
  Hi,

  I am doing this:

  Host with Ubuntu 22.04, lxd 5.10-b392610 (snap), running several
  virtual machines as LXD containers (Ubuntu 22.04 as well).

  I do use LXD profiles with cloud-init settings (packages, runcmd, ...)
  in the user.user_data of LXD profiles. works as expected.


  Since I am using different hosts in different networks in different
  timezones I am setting these things (timezone, apt-proxy, users) with
  a cloud-init script in the user.vendor-data settings of the LXD
  default profile. Works as well for most settings, i.e. timezone,
  proxy, users.

  But it does not work for setting the DNS search domain.

  Neither

  resolv_conf:
    nameservers: ['..some..ip']
    searchdomains:
      - domain1
      - domain2

  nor

  network:
    version: 2
    ethernets:
      eth0:
        match:
          name: eth*
        nameservers:
          search: [fritz.box]

  
  seem to work. 

  /etc/resolv.conf just has

  nameserver 127.0.0.53
  options edns0 trust-ad
  search lxd

  
  and /etc/systemd/resolve.conf 
  #Domains=

  
  regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2004131/+subscriptions