[SOLVED] DNS Issues with systemd-resolved.service

DNSSEC prevents to resolve DNS-Zones like *.local. On Linux Mint for example this leads to a DNS-Problem in company wide networks with for example domain.local domains.

Image for post
Image for post
Pic by thesslstore.com

I lastly found a solution while setting up my colleagues new laptop which where installed with the latest Linux Mint (19.x) Ubuntu.

The problem we encounterd was that we have different domains where some inhouse where ending with .local . So DNSSEC obviously rightly don’t like.

Here is our solution:

First unlink /etc/resolv.conf or delete, rename it.

Then link it to the dynamic systemd-resolved.serviceconfiguration.

In the next step we will disable DNSSEC. Therefore you need to edit your /etc/systemd/resolved.conf to something like that:

Lastly find in /etc/nsswitch.conf the hosts: line which tells the sequence in how your device should resolve.

Find the line and replace it with hosts: files dns . This will resolve your /etc/resolv.conf first and 2nd asking your specified DNS-Server.


Working as a IT-Operations engineer at NeXenio, a spin-off by Hasso-Plattner-Institute for products around a digitial workspace.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store