18.04 Desktop LTS DNS lookup problem

Asked by Uwe

Hi,

I am using te latest Ubuntu Mate Desktop 18.04 LTS release and have issues getting local DNS to work.
In my network I maintain a central router instance that povides DHCP and DNS successfully over many years. The DHCP assigns a valid address and correct DNS information to my above mentioned network client. However DNS resolution does not work for DNS records maintained in my router for my local network.
See here: (local DNS server on .3.1)

uho@Asus:~/Schreibtisch$ systemd-resolve --status
Global
          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
                      20.172.in-addr.arpa
                      21.172.in-addr.arpa
                      22.172.in-addr.arpa
                      23.172.in-addr.arpa
                      24.172.in-addr.arpa
                      25.172.in-addr.arpa
                      26.172.in-addr.arpa
                      27.172.in-addr.arpa
                      28.172.in-addr.arpa
                      29.172.in-addr.arpa
                      30.172.in-addr.arpa
                      31.172.in-addr.arpa
                      corp
                      d.f.ip6.arpa
                      home
                      internal
                      intranet
                      lan
                      local
                      private
                      test

Link 2 (wlp2s0)
      Current Scopes: DNS
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no
         DNS Servers: 192.168.3.1
uho@Asus:~/Schreibtisch$

uho@Asus:~/Schreibtisch$ nslookup filou
Server: 127.0.0.53
Address: 127.0.0.53#53

** server can't find filou: SERVFAIL

uho@Asus:~/Schreibtisch$ nslookup filou 192.168.3.1
Server: 192.168.3.1
Address: 192.168.3.1#53

Non-authoritative answer:
Name: filou
Address: 192.168.3.10

uho@Asus:~/Schreibtisch$ nslookup 192.168.3.10
10.3.168.192.in-addr.arpa name = filou.

Authoritative answers can be found from:

uho@Asus:~/Schreibtisch$

The example above shows that DNS forward lookup for "filou" does not work, only reverse lookup works.
The same behavior with explicit DNS setting in network manager.

Any idea what's wrong? To me this looks weirdly broken.

BTW: Old school setting in /etc/resolv.conf works like a charm.

BR
Uwe

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#1

Try:

echo "nameserver 192.168.3.1" | sudo tee -a /etc/resolvconf/resolv.conf.d/head > /dev/null

Should do it. It'll stay between reboots too

Revision history for this message
Uwe (madscientist42) said :
#2

Hi Andrew,

thanks for coming back with this answer, but as I write in my question, I already came across that workaround.
For some reason this workaround is an ugly one, at least if you travel with a laptop and connect to many different networks.

There is some best practice that is badly treated:
1) If the user specifies a DNS, this is the one to be used. Not taking it into account is not an option!
2) If systemd-resolved thinks it should use a different DNS, then there needs to be a tick mark a user can opt-in for
3) A system should never establish data connection (and be it DNSSEC) that shares user data without explicit agreement

In the end there is a reason for a local DNS and a reason why DHCP has an option to deliver DNS information. You can't just not take the intention into account, because you are breaking very basic functionality!
Besides that I am questioning the approach to release a LTS version with stability as the maxime and then deliver this.

One can't change (break!) basic functionality without intimidating your user base.

BR
Uwe

Revision history for this message
Uwe (madscientist42) said :
#3
Revision history for this message
actionparsnip (andrew-woodhead666) said :
#4

I suggest you report a bug.

I've no problem here.

Can you help with this problem?

Provide an answer of your own, or ask Uwe for more information if necessary.

To post a message you must log in.