OMV 5 does not resolve single-name (dotless) hostnames on the local network whereas OMV4 does.

Hi,

So I have a couple of vanilla OMV 5 boxes join the fold on two different networks & two different domains.

Let's say these local networks are mydomain1 and mydomain2. The domain names are configured correctly in the webgui. Network config is ipv4 dhcp ipv6 disabled.

I noticed common to both OMV5 installs out of the tin from a shell the following behaviour:

host someclient

would fail whereas

host someclient.mydomain1
host someotherclient.mydomain2

would succeed and resolve a client on the local network/domain to the correct ip.

On my OMV4 systems both of these would resolve correctly out of the tin as expected.

I fixed this by adding the line:

Domains=mydomain1

to /etc/systemd/resolved.conf

(and of course mydomain2 on the second box)

So my whole file now looks like this:

cat /etc/systemd/resolved.conf

#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.
#
# Entries in this file show the compile time defaults.
# You can change settings by editing this file.
# Defaults can be restored by simply deleting this file.
#
# See resolved.conf(5) for details

[Resolve]
#DNS=
#FallbackDNS=
Domains=mydomain1
#LLMNR=yes
#MulticastDNS=yes
#DNSSEC=allow-downgrade
#DNSOverTLS=no
#Cache=yes
#DNSStubListener=yes
#ReadEtcHosts=yes

And now the behaviour of the OMV5 installations matches that of the OMV4 ones.

I believe this to be down to the default behaviour of systemd-resolver.service which OMV5 has moved to?

My question is should this be handled by the domain config in the webgui? If so then I would suggest this is a bug.

If, however, it was intended that moving OMV5 to systemd should inherit the default behaviour of systemd then it's more of a gotcha because the behaviour is now different than that of OMV4.

Either way here it is for those that may also come accross this issue.

Regards,

Andy.