Public bug reported:

Mint 19 (Ubuntu Bionic) 
Laptop so Using NetworkManager, and connecting wirelessly to LAN
Upgraded from Mint 18.3 so using resolvconf...

Versions:
network-manager: 1.10.6-2ubuntu1.1
resolvconf: 1.79ubuntu10.18.04.3 or 1.79ubuntu10.18.04.2
systemd: 237-3ubuntu10.15

dns is specified in NetworkMananager as 192.168.2.1
the dns is a router, and has static ips assigned to certain hosts on my lan...

$cat resolv.conf
nameserver 127.0.0.53
search phs
options edns0

$ nslookup phspi05
Server:         127.0.0.53
Address:        127.0.0.53#53

** server can't find phspi05: SERVFAIL

If I explicity specify the dns:

$ nslookup phspi05 192.168.2.1
Server:         192.168.2.1
Address:        192.168.2.1#53

Non-authoritative answer:
Name:   phspi05
Address: 192.168.2.35

I get the correct ip address...

Same with dig...

I would expect that the nameserver set in network-manager would be
used....

>From tail of $ systemd-resolve --status

Link 2 (wlp2s0)
      Current Scopes: DNS
       LLMNR setting: yes
MulticastDNS setting: no
      DNSSEC setting: no
    DNSSEC supported: no
         DNS Servers: 192.168.2.1
          DNS Domain: phs

So the dns address had been picked up from NetworkManager, but
apparently is not being used...

Thought it might be related to this bug:
https://bugs.launchpad.net/ubuntu/bionic/+source/resolvconf/+bug/1817903

So installed the proposed fix, but no change. I also tried removing
package resolvconf, again no change...

** Affects: resolvconf (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821491

Title:
  DNS lookup fails for local hosts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1821491/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to