# Mender Server on a local network using mDNS with a board using systemd-networkd

**URL:** <https://hub.mender.io/t/mender-server-on-a-local-network-using-mdns-with-a-board-using-systemd-networkd/291>\
**Category:** General Discussions\
**Created:** [March 4, 2019, 5:57pm UTC](https://hub.mender.io/t/mender-server-on-a-local-network-using-mdns-with-a-board-using-systemd-networkd/291 "2019-03-04T17:57:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![martin](https://avatars.discourse-cdn.com/v4/letter/m/73ab20/32.png) [@martin](https://hub.mender.io/u/martin)\
**Post date:** [March 4, 2019, 5:57pm UTC](https://hub.mender.io/t/mender-server-on-a-local-network-using-mdns-with-a-board-using-systemd-networkd/291/1 "2019-03-04T17:57:47Z")

</div>

Hi,

I thought I would share this in case anyone else comes up against this problem. We were trying out the mender server with a local domain, say test.mender.local and using mDNS within systemd (not avahi) and we found that although we could resolve the address using

```auto
systemd-resolve test.mender.local

```

you couldn’t ping the address. The networkd configuration required mDNS turning on, this was our _/etc/systemd/network/20-wired.network_ configuration file:

```auto
[Match]
Name=eth0

[Network]
DHCP=ipv4
MulticastDNS=true

```

What I found was that I had to install the resolve NSS plugin libnss-resolve that is part of the systemd package. In Yocto we used:

```auto
IMAGE_INSTALL += "${@bb.utils.contains('DISTRO_FEATURES', 'systemd', 'libnss-resolve', '', d)}"

```

And then customise the nsswitch.conf to use it, ie have the resolve keyword in the hosts section, something like

```auto
hosts: files resolve [!UNAVAIL=return] dns myhostname

```

and now it will use the resolve plugin and hence systemd to resolve addresses before trying other methods. Hopefully you should now be able to ping your local domain address.