Search domains in Debian 8 with systemd-resolved

dhcplinux-networkingsystemd

I'm running Debian 8 + systemd215. I'm trying to setup domain suffix to be appended automatically, when I ping other hosts in LAN. Before systemd I'd just add below line to:
#/etc/resolv.conf search sub2.sub1.mydomain

But now on modern system resolve.conf is linked to /var/run/systemd/resolve/resolv.conf. So added below lines:
#/etc/systemd/network/eth.network [DHCP] UseDomains=true #/etc/systemd/resolved.conf [Resolve] Domains=sub2.sub1.mydomain

Restart networkd/resolved and got below messages in journal:
systemd-networkd[15171]: [/etc/systemd/network/eth.network:9] Unknown lvalue 'UseDomains' in section 'DHCP' ... systemd-resolved[16332]: [/etc/systemd/resolved.conf:12] Unknown lvalue 'Domains' in section 'Resolve'

I found, this might be actually a bug in systemd prior to 228. I do not see any fresh versions of systemd available for my Debian from stable repo. So should I just go and unlink /etc/resolve.conf and add searched domains in old fashioned way? Or am I missing something here?

Best Answer

Welcome to Serverfault.

The list of all directives available in your currently installed version of systemd is available in man systemd.directives. Search in that document to see if "Domains" is available in your version.

If the directives you need are not available, then, yes, you should use the traditional resolver instead of the systemd resolver.

Related Solutions

Systemd – How to Set Environment Variable in Service

Times change and so do best practices.

The current best way to do this is to run systemctl edit myservice, which will create an override file for you or let you edit an existing one.

In normal installations this will create a directory /etc/systemd/system/myservice.service.d, and inside that directory create a file whose name ends in .conf (typically, override.conf), and in this file you can add to or override any part of the unit shipped by the distribution.

For instance, in a file /etc/systemd/system/myservice.service.d/myenv.conf:

[Service]
Environment="SECRET=pGNqduRFkB4K9C2vijOmUDa2kPtUhArN"
Environment="ANOTHER_SECRET=JP8YLOc2bsNlrGuD6LVTq7L36obpjzxd"

Also note that if the directory exists and is empty, your service will be disabled! If you don't intend to put something in the directory, ensure that it does not exist.

For reference, the old way was:

The recommended way to do this is to create a file /etc/sysconfig/myservice which contains your variables, and then load them with EnvironmentFile.

For complete details, see Fedora's documentation on how to write a systemd script.

Find the location of a systemd unit file service

For units that are defined in actual, static files, this can be seen in systemctl status:

$ systemctl status halt-local.service
● halt-local.service - /usr/sbin/halt.local Compatibility
   Loaded: loaded (/lib/systemd/system/halt-local.service; static)
   Active: inactive (dead)

But there are units that are not defined by files, e.g. with systemd-cron installed. These have no useful location listed with status:

$ systemctl status cron-jojo-0.timer
● cron-jojo-0.timer - [Cron] "*/10 * * * * ..."
   Loaded: loaded (/var/spool/cron/crontabs/jojo)
   Active: active (waiting) since Mon 2015-05-18 14:53:01 UTC; 9min ago

In either case, though, the FragmentPath field is educating:

$ systemctl show -p FragmentPath cron-daily.service
FragmentPath=/lib/systemd/system/cron-daily.service
$ systemctl show -p FragmentPath cron-jojo-0.service
FragmentPath=/run/systemd/generator/cron-jojo-0.service
$ systemctl show -p FragmentPath halt-local.service
FragmentPath=/lib/systemd/system/halt-local.service

Best Answer

Related Solutions

Systemd – How to Set Environment Variable in Service

Find the location of a systemd unit file service

Related Topic