0

I have my own DNS server, DHCP sets it in any host on the LAN.

I have just installed a new Ubuntu 17.10 laptop

This command

nslookup abox

Can't find the IP of abox (it is in DNS)

nslookup
> server 192.168.1.30
abox

Returns the correct address

systemd-resolve --status

claims to be using 

DNS Servers: 192.168.1.30

But it obviously is not, its using 127.0.0.53, I can see the traffic in tcpdump.

So how do I tell systemd to stop messing with the DNS config that DHCP has told it to use and to actually start using the DNS server it claims to be using?

teknopaul
  • 2,137

1 Answers1

0

This post has an answer.

rm -f /etc/resolv.conf
ln -s /run/systemd/resolve/resolv.conf /etc/resolv.conf
reboot

Now I can resolve DNS properly again.

Elder Geek
  • 36,752
teknopaul
  • 2,137