Another note on this: today I'm visiting a customer and the issue of "default DNS" came up. The normal use case for MAAS is "everything points to the MAAS server", which implies no special DNS setup on a per-subnet/per-interface basis.
The way this is currently accomplished with curtin is to write the default DNS servers into the loopback interface declaration in /etc/network/interfaces.
Is it possible to do something similar with networkd?
Another way I've solved this personally is to create a bridge that isn't connected to any external interfaces and place the configuration there, such as:
Another note on this: today I'm visiting a customer and the issue of "default DNS" came up. The normal use case for MAAS is "everything points to the MAAS server", which implies no special DNS setup on a per-subnet/ per-interface basis.
The way this is currently accomplished with curtin is to write the default DNS servers into the loopback interface declaration in /etc/network/ interfaces.
Is it possible to do something similar with networkd?
Another way I've solved this personally is to create a bridge that isn't connected to any external interfaces and place the configuration there, such as:
# Host-only bridge for containers.
bridge_ ports none
bridge_ waitport 0
dns-nameserver 8.8.8.8
dns-nameserver 8.8.4.4
iface host0 inet manual
bridge_stp off
bridge_fd 0