Jtdcftul

Try editing /etc/systemd/resolved.conf, adding your desired DNS server:

change this:

[Resolve]

#DNS=

to this (but use the one you want - this is an example):

[Resolve]

DNS=192.168.1.152

after that, restart the service:

service systemd-resolved restart

And when you check the status you should see

$ systemd-resolve --status

Global

         DNS Servers: 192.168.1.152



      DNSSEC NTA: 10.in-addr.arpa

                  16.172.in-addr.arpa

                  168.192.in-addr.arpa

                  17.172.in-addr.arpa

                  18.172.in-addr.arpa

                  19.172.in-addr.arpa

Known systemd bug.

Temporary workaround with no need to reconfigure if the DNS IP's changes:

sudo rm -f /etc/resolv.conf

sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf

reboot

I put together a script that works around the issue of Netplan not currently supporting the ability to supersede DHCP supplied DNS servers and domain search order. It creates the Netplan yaml file and configures systemd-resolved to work as expected.

################## Start Netplan config (renderer: NetworkManager)

#  Some useful commands for customisation

# NetConn=$(nmcli device show|grep GENERAL.CONNECTION|head -n1|awk '{print $2}')

# IP=$(nmcli device show|grep IP4.ADDRESS|head -n1|awk '{print $2}')

# GATEWAY=$(nmcli device show|grep IP4.GATEWAY|head -n1|awk '{print $2}')

# sed -i 's/renderer: networkd/renderer: NetworkManager/' //etc/netplan/01-netcfg.yaml

######################################

systemctl start NetworkManager

NIC=$(nmcli device show|grep GENERAL.DEVICE|head -n1|awk '{print $2}')



#####   create Netplan yaml config file

cat >/etc/netplan/01-netcfg.yaml <<EOF 

# This file describes the network interfaces available on your system

# For more information, see netplan(5).

  network:

   version: 2

   renderer: NetworkManager

   ethernets:

EOF

echo "    ${NIC}:" >> /etc/netplan/01-netcfg.yaml

cat >>/etc/netplan/01-netcfg.yaml <<EOF

      dhcp4: yes

      nameservers:

        search: [abc.domain.edu, def.domain.edu]

        addresses: [10.10.11.22, 10.10.11.23]



EOF



#work around DNS resolv bug

systemctl stop systemd-resolved

sed -i 's/#DNS=/DNS=10.10.11.22 10.10.11.23/' /etc/systemd/resolved.conf

sed -i 's/#Domains=/Domains=abc.domain.edu def.domain.edu' /etc/systemd/resolved.conf

systemctl start systemd-resolved

systemctl restart NetworkManager

netplan apply

reboot

############### End Netplan Config

The solution that worked for me is posted here on my blog

Use nano editor to edit these 2 files

nano /etc/resolv.conf

nano /etc/resolvconf/resolv.conf.d/head

Add DNS servers you want to use

nameserver 9.9.9.9

nameserver 127.0.0.1

Then restart the service

service systemd-resolved restart

Final check:

cat /etc/resolv.conf

Do nslookup

nslookup google.com 

i just used this and it fixed the problem on my laptop at home, but some time in the future when I am out of my home network I can see that it will cause problems, because the primary and secondary dns server will still be my home servers with their lan addresses.

I finally got a solution for this problem for ubuntu 17.10. By default this version of Ubuntu uses systemd-resolved, which I hope is going to be stable for the next versions.

In order to use custom dns instead of the local systemd-resolved cache, do the following:

1. add new nameservers. Edit the file in /etc/systemd/resolved.conf as sudoer. Here I've commented out the DNS entry and placed my dns
   
[Resolve]
DNS=10.96.0.10 8.8.8.8 8.8.4.4





2. cancel the actual symlink to /etc/resolv.conf



3. create a new symlink sudo ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
   


4. restart the service sudo service systemd-resolved restart
   


5. restart the network manager sudo systemctl restart networking
   

And now if you dig to a name provided by your add dns, you should see the record resolved dig nexus.default.svc.cluster.mydomain

Last step is to update the order of resolution in /etc/nsswitch.conf, by placing the dns before the mdns4_minimal

hosts           files dns mdns4_minimal [NOTFOUND=return] resolve [!UNAVAIL=return] myhostname

Your /etc/resolv.conf is not any problem. systemd-resolved just defaults to unconfigured, so it fails all lookups. Feel free to rant about Unconfigured vs A Reasonable Default.

Manually add nameservers to systemd-resolved.
(editing per comment below to add mkdir, correct path /etc not /lib, in order to survive system updates)

sudo mkdir -p /etc/systemd/resolved.conf.d

sudo nano /etc/systemd/resolved.conf.d/00-my-dns-server-is.conf

Add:

[Resolved]

Cache=yes

DNS=192.168.1.152

Then...

sudo systemctl daemon-reload

systemd-resolved is smart, but, unconfigured as it is, by package maintainers, it just LOOKS stupid because package maintainers do not believe in A Reasonable Default. We can put 13 internet root servers in there aka "djb way", or 10 opennic servers: https://pastebin.com/JBfYVVtG or the three fastest opennic servers, as measured by namebench. Plus ISP nameservers, sure. Plus Google, sure. systemd-resolved is not the problem. I am the problem.

I have the same problem. Each reboot, nothing will resolve. I've uninstalled everything and reinstalled it about 50 times already. It's simply just broken.

so the fix is.... "just apply a few settings each time you boot your pc, which allows 90% of host names to resolve but wget and apt-get updates and upgrades will fail randomly for no reason"

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=

#LLMNR=yes

#MulticastDNS=yes

#DNSSEC=no

#Cache=yes

#DNSStubListener=udp

When using Ubuntu 17.10 Desktop, you have to edit the one file that says DO NOT EDIT THIS FILE BLAH BLAH BLAH

well that's the ONLY way it works~!

root@nas:~# cat /etc/resolv.conf

# This file is managed by man:systemd-resolved(8). Do not edit.

#

# 127.0.0.53 is the systemd-resolved stub resolver.

# run "systemd-resolve --status" to see details about the actual nameservers.

nameserver 8.8.8.8

So remove the 127.0.0.53 IP as the name server and enter another one, google for example. It appears my actual DNS IP address doesn't resolve host names either (even though it works on 10 other machines and devices in the house), but google's works fine.