$ 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: . 3600 IN 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. 6899 IN 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: b088880c84bd6596 (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 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/systemd/+bug/1821491/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
