$ 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
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

Reply via email to