[Bug 1875044] Re: Host name not resolved

[Rimas Kudelis]

$ systemd-resolve --status
Global
       LLMNR setting: no
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: no
    DNSSEC supported: no
          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 184 (br-c5c554540e93)
      Current Scopes: none
DefaultRoute setting: no
       LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: no
    DNSSEC supported: no

Link 909 (veth145b083)
      Current Scopes: none
DefaultRoute setting: no
       LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: no
    DNSSEC supported: no

Link 907 (veth259d5e7)
      Current Scopes: none
DefaultRoute setting: no
       LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: no
    DNSSEC supported: no

Link 905 (veth70c5229)
      Current Scopes: none
DefaultRoute setting: no
       LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: no
    DNSSEC supported: no

Link 903 (veth754adf7)
      Current Scopes: none
DefaultRoute setting: no


$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 19.10
Release:	19.10
Codename:	eoan


$ apt policy systemd
systemd:
  Įdiegta:    242-7ubuntu3.7
  Kandidatas: 242-7ubuntu3.7
  Versijų lentelė:
 *** 242-7ubuntu3.7 500
        500 http://lt.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     242-7ubuntu3.6 500
        500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages
     242-7ubuntu3 500
        500 http://lt.archive.ubuntu.com/ubuntu eoan/main amd64 Packages


I don't think I have configured anything WRT how systemd-resolved works. All configuration comes from DHCP.

I have configured and sometimes a couple VPN networks use on my machine,
these have some explicit configuration on them (I'm (hopefully) not
using them as default route and I had to configure IPSEC algorithms
manually to be able to connect), but the issue manifests regardless of
whether or not I'm connected to them, so I think it's safe to assume
they don't have any effect on it.

I'm planning to upgrade to Ubuntu 20.04 within a few weeks.

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

Title:
  Host name not resolved

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  Systemd-resolved fails to resolve a host which has a private IP address, even though its DNS entry is public. This happens even when I am connected to a VPN where the host resides.
  Interestingly, if I manually issue a `host -a` request, the host gets resolved, and further resolution works until its cached entry times out.

  Here's some hopefully helpful output of me running `nslookup` and
  `host`:

  # nslookup
  > presto.lmta.lt
  Server:		127.0.0.53
  Address:	127.0.0.53#53

  Non-authoritative answer:
  *** Can't find presto.lmta.lt: No answer
  > server 8.8.8.8
  Default server: 8.8.8.8
  Address: 8.8.8.8#53
  > presto.lmta.lt
  Server:		8.8.8.8
  Address:	8.8.8.8#53

  Non-authoritative answer:
  Name:	presto.lmta.lt
  Address: 10.41.0.118
  > server 127.0.0.53
  Default server: 127.0.0.53
  Address: 127.0.0.53#53
  > presto.lmta.lt
  Server:		127.0.0.53
  Address:	127.0.0.53#53

  Non-authoritative answer:
  *** Can't find presto.lmta.lt: No answer
  [^D pressed]

  # host presto.lmta.lt
  [no output at all. I immediately run the next command]

  # host -a presto.lmta.lt
  Trying "presto.lmta.lt"
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20532
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

  ;; QUESTION SECTION:
  ;presto.lmta.lt.			IN	ANY

  ;; ANSWER SECTION:
  presto.lmta.lt.		3599	IN	A	10.41.0.118

  Received 48 bytes from 127.0.0.53#53 in 57 ms

  [then immediately afterwards:]
  # host presto.lmta.lt
  presto.lmta.lt has address 10.41.0.118

  # nslookup
  > presto.lmta.lt
  Server:		127.0.0.53
  Address:	127.0.0.53#53

  Non-authoritative answer:
  Name:	presto.lmta.lt
  Address: 10.41.0.118

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