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 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 [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
