[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
> setting the router's search domain(s) will have *no effect at all* on > lookups from any other system well - this does depend on your specific dns nameserver program and configuration; so I shouldn't say this without qualification :) It's possible to have your router's dns use local lookups, in various ways. -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Invalid Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
> Sorry thought I was using dig at your request... yes, sorry - dig is useful *but* it does only what you ask it specifically to do (i.e. lookup the specific hostname you ask it for, without appending any search domains to it). this is different from everything else on your system, which uses getaddrinfo(), which will append search domains listed in /etc/resolv.conf. > ping often works when nslookup fails i can't say *exactly* why this is, but I suspect it's because you had two nameservers listed in /etc/resolv.conf; your router (which *will* resolve the hostname without any domain suffix) and your local systemd- resolved resolver (which *will not* resolve the hostname without a domain suffix, since it won't pass the "single label" hostname to your router nameserver). i believe (don't remember the specifics of the glibc internals tho) that getaddrinfo() will do round-robin queries of each nameserver you list in /etc/resolv.conf, so it may be random chance that one thing looks up your host right, and the next request doesn't. > so clearly the domain is set that will let you do "single label" lookups *from your router only*. setting the router's search domain(s) will have *no effect at all* on lookups from any other system. just make sure: -your router's dhcp configuration includes your local subnet domain (i.e. provides it to your dhcp clients) -your router's dnsmasq (or whatever public nameserver program) has your local subnet hosts *including local subnet domain* defined -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Invalid Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
Thanks again Dan for taking the time to explain. > stop using dig to debug your system. Sorry thought I was using dig at your request... I was originally using nslookup and ping to find out why I couldn't browse to the server on phspi05 (phspi05 is actually controlling the heating and cooling in my glasshouse) and confusingly to me they give different results, ping often works when nslookup fails (as is currently the case on the desktop) > you don't need the router configured to resolve the "single label" (without > .phs) hostname ... I have managed to telnet into the router: # cat /etc/resolv.conf domain phs nameserver 208.67.222.222 nameserver 212.159.6.10 so clearly the domain is set, but if I remove the single label entry from the router even ping fails from the desktop (but still works on the laptop) and it seems that when providing an address via dhcp (e.g. to the laptop) the router puts both phs09 and phs09.phs in /etc/hosts, so I guess the router needs it... -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Invalid Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
> So it seems to me that lookups by systemd-resolved > are failing to lookup the hostname on the local DNS > (even if this is by design) yes, this is by design. systemd-resolved never forwards "single label" addresses to upstream nameservers. > If the router has the hostname AND domainname defined: > phspi05 192.168.2.35 > phspi05.phs 192.168.2.35 you don't need the router configured to resolve the "single label" (without .phs) hostname (unless your router doesn't have 'phs' in its resolv.conf search list, and you need to look up the hostname from the router itself). > on laptop > dig phspi05 = fails stop using dig to debug your system. the behavior above is correct (dig *should* fail when querying the local systemd-resolved resolver without using .phs domain suffix). Instead try using a program that uses getaddrinfo(), like nslookup, ping, or even host. e.g.: $ host phspi05 > I guess I have a workaround to manually edit resolv.conf, and as I don't > reboot that often it is not a big issue, but it doesn't feel right somehow. it isn't right, and you don't need to. Just make sure your router delivers your domain as part of its dhcp reply, and you will be fine. Your resolv.conf will contain your local domain in its 'search' and all programs on your system using getaddrinfo() and friends will correctly look up any address with your domain appended. -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Invalid Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
Thankyou for all the attention to this and the explanations Dan, but now I am also confused... I tend to think that if my desktop is able to successfully lookup the host on the router (as per https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1817903) then I should expect that my laptop on the same lan, should also be able to do so, hence to me it is still a bug... So to clarify for me, if nothing else: If the router dns only has the hostname defined, i.e. phspi05 192.168.2.35 Lookups by the desktop (no NetworkManager, fixed IP) with resolv.conf containing: nameserver 192.168.2.1 nameserver 127.0.0.53 dig phspi05 = success dig phspi05.phs = fail Lookups by the laptop (with NetworkManager, dhcp assigned IP) with resolv.conf containing: nameserver 127.0.0.53 search phs dig phspi05 = fail dig phspi05.phs = fail dig phspi05 @192.168.2.1 = success dig phspi05.phs @192.168.2.1 = fail If I manually edit resolv.conf on the laptop so that it looks like nameserver 192.168.2.1 nameserver 127.0.0.53 search phs dig phspi05 = success So it seems to me that lookups by systemd-resolved are failing to lookup the hostname on the local DNS (even if this is by design) Whatever way I look at it, I have an inconsistency between computers on the same network. If the router has the hostname AND domainname defined: phspi05 192.168.2.35 phspi05.phs 192.168.2.35 then on the desktop dig phspi05 = success dig phspi05.phs = success on laptop dig phspi05 = fails dig phspi05.phs = success I guess I have a workaround to manually edit resolv.conf, and as I don't reboot that often it is not a big issue, but it doesn't feel right somehow. -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Invalid Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
> $ dig phspi05.phs @192.168.2.1 ... > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21263 hmm, so, i'm confused now, in the description you said dig works when querying your router directly? I guess that's not the case? It certainly seems like this is not a issue with systemd - your problem appears to be with your router dns configuration. I'll mark this bug as invalid, but let me know if you disagree. > So is it perhaps that my naive expectation that without a domain the host is > assumed to be local is not consistently followed by different > programs/devices? Appending of the "search domains" is done only through the getaddrinfo() (and related) glibc functions. This is the call that uses the /etc/resolv.conf file for configuration to perform its lookup. You can see "man resolv.conf" for specific details on the process, but in most cases it will lookup the hostname you ask for first, and then if that fails it will try looking up the hostname using each 'search' domain you specify. Since modern systems using systemd almost always configure resolv.conf to send all traffic to the local stub resolver (i.e. 127.0.0.53), this in effect means systemd-resolved is responsible for actually talking to all upstream name servers. Note that any program that *does not* use getaddrinfo() completely bypasses this and is free to perform lookups however it wants; dig does just that, by querying *exactly* what you are searching for, to *exactly* the nameserver you specify. You can tell dig to use any search domains specified in /etc/resolv.conf, with the +search parameter; by default it does not use any search domains, and queries only what you ask it for. > Also I now realise that my laptop doesn't know what domain it is part of: > $ domainname > (none) Unless you don't have 'domain' or 'search' defined in /etc/resolv.conf, this doesn't matter for dns resolution. ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Invalid Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
** Changed in: systemd (Ubuntu) Status: Incomplete => 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: New Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
$ dig phspi05.phs ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> phspi05.phs ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61787 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;phspi05.phs. IN A ;; Query time: 29 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Apr 17 10:08:48 BST 2019 ;; MSG SIZE rcvd: 40 $ dig phspi05.phs @192.168.2.1 ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> phspi05.phs @192.168.2.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21263 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;phspi05.phs. IN A ;; AUTHORITY SECTION: . 3600IN SOA a.root-servers.net. nstld.verisign-grs.com. 2019041700 1800 900 604800 86400 ;; Query time: 20 msec ;; SERVER: 192.168.2.1#53(192.168.2.1) ;; WHEN: Wed Apr 17 10:10:11 BST 2019 ;; MSG SIZE rcvd: 115 Hmm... so that is curious... this is making me think, so I have another local host specified on the router DNS, but it is specified with then host and local domain, i.e. on the router I have: sjr05x 192.168.2.20 sjr05x.phs 192.168.2.20 And dig results: $ dig sjr05x ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> sjr05x ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 15618 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;sjr05x.IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Apr 17 10:15:06 BST 2019 ;; MSG SIZE rcvd: 35 $ dig sjr05x @192.168.2.1 ;; Warning: Message parser reports malformed message packet. ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> sjr05x @192.168.2.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25027 ;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: ddfb8b62c3075f35 (echoed) ;; QUESTION SECTION: ;sjr05x.IN A ;; ADDITIONAL SECTION: sjr05x. 199150 IN A 192.168.2.20 ;; Query time: 7 msec ;; SERVER: 192.168.2.1#53(192.168.2.1) ;; WHEN: Wed Apr 17 10:19:32 BST 2019 ;; MSG SIZE rcvd: 63 $ dig sjr05x.phs ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> sjr05x.phs ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4826 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;sjr05x.phs.IN A ;; ANSWER SECTION: sjr05x.phs. 6899IN A 192.168.2.20 ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Wed Apr 17 10:20:16 BST 2019 ;; MSG SIZE rcvd: 55 $ dig sjr05x.phs @192.168.2.1 ;; Warning: Message parser reports malformed message packet. ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> sjr05x.phs @192.168.2.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52715 ;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: b00c84bd6596 (echoed) ;; QUESTION SECTION: ;sjr05x.phs.IN A ;; ADDITIONAL SECTION: sjr05x.phs. 199217 IN A 192.168.2.20 ;; Query time: 5 msec ;; SERVER: 192.168.2.1#53(192.168.2.1) ;; WHEN: Wed Apr 17 10:20:39 BST 2019 ;; MSG SIZE rcvd: 67 So is it perhaps that my naive expectation that without a domain the host is assumed to be local is not consistently followed by different programs/devices? Also I now realise that my laptop doesn't know what domain it is part of: $ domainname (none) but then neither does my desktop where the lookups work (not using networkmanager), and explicitly setting it seems to have no effect. -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Incomplete Bug description: 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 $ nsloo
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
> $ dig phspi05 @192.168.2.1 > ;; Warning: Message parser reports malformed message packet. that's generally not good... > phspi05. 69314 IN A 192.168.2.35 ok, this is resolving the "single label" name. systemd-resolved never forwards lookups of single-label names (except for LLMNR, I believe). So, based on earlier output in this bug showing your configured search domain, let's see what the output looks like when we include the search domain: $ dig phspi05.phs $ dig phspi05.phs @192.168.2.1 -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Incomplete Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
Sorry for slow response Dan, here is the output: $ dig phspi05 @192.168.2.1 ;; Warning: Message parser reports malformed message packet. ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> phspi05 @192.168.2.1 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2588 ;; flags: qr; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ; COOKIE: 79718a61fe0a1b8b (echoed) ;; QUESTION SECTION: ;phspi05. IN A ;; ADDITIONAL SECTION: phspi05.69314 IN A 192.168.2.35 ;; Query time: 9 msec ;; SERVER: 192.168.2.1#53(192.168.2.1) ;; WHEN: Mon Apr 15 22:15:35 BST 2019 ;; MSG SIZE rcvd: 64 And for completeness, without specifying the server: $ dig phspi05 ; <<>> DiG 9.11.3-1ubuntu1.5-Ubuntu <<>> phspi05 ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 37781 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 65494 ;; QUESTION SECTION: ;phspi05. IN A ;; Query time: 0 msec ;; SERVER: 127.0.0.53#53(127.0.0.53) ;; WHEN: Mon Apr 15 22:24:42 BST 2019 ;; MSG SIZE rcvd: 36 -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Incomplete Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
can you paste the output of dig: $ dig phspi05 @192.168.2.1 -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Incomplete Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
Sorry thought I had responded already: In answer to #5 same result = failure result In answer to #6 For info Router is a Billion BiPAC 7800VDOX Router is set to use public DNS: 208.67.222.222 212.159.6.10 Router is set with domain name of phs Router has a table of static DNS defined: Host IP phspi05 192.168.2.35 etc. -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Incomplete Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
** Changed in: systemd (Ubuntu) Status: New => Incomplete -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: Incomplete Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
> $ 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 > ** server can't find phspi05: NXDOMAIN your upstream ns is returning an address, but NXDOMAIN as well; I'm pretty sure resolved sees that as query failure, and ignores the address that the server returned. What dns server are you using on your router, and how is it set up with your custom host addresses? -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: New Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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
Re: [Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
On Thu, Apr 04, 2019 at 07:27:00PM -, Steve Roberts wrote: > Yes, that sounds correct, your reply made me check, if I do: > nslookup phspi05.phs > I also get the same result... By "same result", you mean the successful result or the failure result? -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: New Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
Yes, that sounds correct, your reply made me check, if I do: nslookup phspi05.phs I also get the same result... -- 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/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: New Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
Ok, so you have no other DNS servers configured. So 192.168.2.1 is the DNS server that's being used, but systemd-resolved doesn't like something about either the request or the response and is not forwarding it. I note that you also say that this only fails for *local* hosts; i.e. if I pay more attention, I see that the name that is being resolved has no domain name at all. So it looks to me like systemd-resolved is unhappy with this in particular and this is why it's not giving you results. Reassigning to systemd. ** Package changed: resolvconf (Ubuntu) => systemd (Ubuntu) ** Changed in: systemd (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1821491 Title: DNS lookup fails for local hosts Status in systemd package in Ubuntu: New Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+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
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
Okay thanks for the attention, full output below: $ systemd-resolve --status Global DNS Domain: phs 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.2.1 DNS Domain: ~. phs $ nslookup phspi05 Server: 127.0.0.53 Address:127.0.0.53#53 ** server can't find phspi05: SERVFAIL if I specify the dns in nslookup $ 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 ** server can't find phspi05: NXDOMAIN and the contents of resolv.conf $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN # 127.0.0.53 is the systemd-resolved stub resolver. # run "systemd-resolve --status" to see details about the actual nameservers. nameserver 127.0.0.53 search phs If I manually edit resolv.conf to the local dns, nslookup, ping etc. work as expected (until the next reboot of course) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1821491 Title: DNS lookup fails for local hosts Status in resolvconf package in Ubuntu: Incomplete Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1821491/+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
[Touch-packages] [Bug 1821491] Re: DNS lookup fails for local hosts
Please show the complete output of systemd-resolve --status on this system. > I would expect that the nameserver set in network-manager would be used If it's not used, that can only be because you have some other nameservers defined that are taking precedence; but we would need to see the complete config to establish this. ** Changed in: resolvconf (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to resolvconf in Ubuntu. https://bugs.launchpad.net/bugs/1821491 Title: DNS lookup fails for local hosts Status in resolvconf package in Ubuntu: Incomplete Bug description: 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... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1821491/+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