How to systemd-resolved


Ubuntu uses the resolvconf program in the standard to configure local DNS resolution.The resolvconf package includes a simple database and a runtime for dynamically modifying name server information.

Typically, the program resolvconf runs through a network interface to push routines such as ifup, ifdown, NetworkManager, dhclient, and pppd, or local name servers such as dnsmasq to update the name server information.

If static IP addresses and DNS records are used on a host, the resolvconf package should be deactivated under Ubuntu, so that the DNS configuration from the dnsmasq daemon is not automatically made, the configuration that has been edited in /etc/resolv.conf and /etc/network/interfaces, will otherwise be overwritten by the resolvconf program.

Disable resolvconf

resolvconf --disable-updates

Disable resolvconf from boot level and quit the program.

systemctl disable systemd-resolved.service
service systemd-resolved stop

Customize The Network Manager with default DNS.

vi /etc/NetworkManager/NetworkManager.conf

Remove the symlink resolv.conf under /etc.

rm /etc/resolv.conf

and create a new resolv.conf file with the name servers. in this example, it’s Google Public DNS.

On a local network or ADS, the internal name servers should be used.

vi /etc/resolv.conf


Delete the resolv.conf file of the systemd configuration program.

rm /etc/systemd/resolved.conf

change the configuration.

service network-manager restart

The name servers can also be entered in the interface configuration.

vi /etc/network/interfaces

auto lo
iface lo inet loopback

auto ens160
iface ens160 inet static
  dns-search my.local

The interface name (ens160) may differ and must correspond to that of the respective host.

The /etc/resolv.conf file should not be missing.

To enable the changed network configuration, it must be read into memory.

/etc/init.d/networking restart


Many network issues are due to incorrect DNS or incorrect configuration of resolver. In a home network there is often no internal DNS, whereby the router or the firewall can be used as a name server, such as the FRITZ!Box. Basically, it should be ensured that the firewall used has a DNS cache, with semi-professional firewalls such as the FortiGate, not every model has such a cache. For open source-based firewalls, on the other hand, most provide a cache through DNS forwarder or dnsmasq.

After changes to the name servers in Windows, the DNS cache should be reset.   Open the prompt.

ipconfig /flushdns

For Linux, the DNS cache can be reset, with one of the following commands, depending on which service is installed.

sudo /etc/init.d/nscd restart
service nscd restart
service nscd reload
sudo /etc/init.d/dnsmasq restart
service dnsmasq restart
rndc reload

In the Mac OS X terminal as root.

lookupd -flushcache

If there is no internal DNS, the name servers of the respective Internet provider can be used, with Swisscom the following are.,,

Example of a name server querying its provider on Windows.

nslookup -type=ns

Non-authoritative response: nameserver = nameserver = internet address =

Example name server lookup query on Linux.

host -t ns name server name server

host & host has address has address has IPv6 address 2a01:2a8:2001:252::11

A ping -n1 resolves addresses to host names with parametersa and4 for IPv4 address.

ping -4 -n 1 -a

Ping runs for with []32 bytes of data:
Response from Bytes=32 Time=32ms TTL=50

Ping statistics for
    Packages: Sent = 1, Receive = 1, Lost = 0
    (0% loss),
Approx. times in millisec.:
    Minimum = 32ms, Maximum = 32ms, Mean = 32ms

How useful was this post?

Click on a star to rate it!

Average rating 0 / 5. Vote count: 0

No votes so far! Be the first to rate this post.

We are sorry that this post was not useful for you!

Let us improve this post!

Tell us how we can improve this post?

Leave a Reply

Your email address will not be published. Required fields are marked *