netplan dhcp domain search not working

Bug #1804473 reported by Kees Bakker
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Netplan
New
Undecided
Unassigned

Bug Description

This system is Ubuntu 18.04, using netplan configuration. In fact, it is a LXD container, if that matters at all.

With a simple netplan dhcp client configuration it does not set the domain search from the DHCP server. The DHCP server is configured correctly, I think, because all other clients setup their domain search as expected.

My netplan config is:

========8X======8X======8X======8X======
network:
  version: 2
  renderer: networkd
  ethernets:
    eth0: {dhcp4: true}
========8X======8X======8X======8X======

Output of systemd-resolve --status is as follows:

========8X======8X======8X======8X======
...
Link 26 (eth0)
      Current Scopes: DNS
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no
         DNS Servers: 172.16.16.39
                      172.16.16.33
          DNS Domain: <mydomain1>
========8X======8X======8X======8X======

That <mydomain1> is really my actual first search domain. There should be another one.

Revision history for this message
Kees Bakker (keestux) wrote :

BTW. I'm suspecting that this one is related https://bugs.launchpad.net/netplan/+bug/1759014

Especially the UseDomains= setting, which is default false (why?)

Revision history for this message
Kees Bakker (keestux) wrote :

To me it seems that netplan (in combination with networkd) is not production ready.

I've switched to the Good Old ifupdown. That works flawlessly.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.