Public bug reported:
On 16.04 I had no problems. On 18.04 systemd-resolved fails to resolve
host name without domain (using nslookup) even though DNS server is
reported by systemd-resolve --status. If to provide DNS to nslookup
explicitly, then the name is resolved.
$ 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 3 (wlp4s0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 2 (enp0s31f6)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 192.168.200.1
$ nslookup sniffer
Server: 127.0.0.53
Address: 127.0.0.53#53
** server can't find sniffer: SERVFAIL
$ nslookup sniffer 192.168.200.1
Server: 192.168.200.1
Address: 192.168.200.1#53
Name: sniffer
Address: 192.168.200.1
** Affects: systemd (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1790628
Title:
systemd from 18.04 fails to resolve name without domain
Status in systemd package in Ubuntu:
New
Bug description:
On 16.04 I had no problems. On 18.04 systemd-resolved fails to resolve
host name without domain (using nslookup) even though DNS server is
reported by systemd-resolve --status. If to provide DNS to nslookup
explicitly, then the name is resolved.
$ 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 3 (wlp4s0)
Current Scopes: none
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
Link 2 (enp0s31f6)
Current Scopes: DNS
LLMNR setting: yes
MulticastDNS setting: no
DNSSEC setting: no
DNSSEC supported: no
DNS Servers: 192.168.200.1
$ nslookup sniffer
Server: 127.0.0.53
Address: 127.0.0.53#53
** server can't find sniffer: SERVFAIL
$ nslookup sniffer 192.168.200.1
Server: 192.168.200.1
Address: 192.168.200.1#53
Name: sniffer
Address: 192.168.200.1
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790628/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
