Clemens Eisserer writes:
> You appear to have given your machine a name that won't resolve via
> public dns (.home doesn't exist), and that you haven't added to the
> local machine lookups.
I am confused. The "home.3" domain is added by my 3g-to-wlan router
for sure via dhcp.
Could it be that dhclient was changed to set also the domain
distributed over dhcp, and this is the reason why this issue started
~1 month ago?
However, when I execute the hostname command, I get "user-pc.erdberg"
- where erdberg is the domain of another network I frequently use the
laptop (and also probably have installed it).
The app tries a DNS lookup for "user-pc". The domain gets appended from
dhclient does update /etc/resolv.conf from dhcp, but it's been doing that
for quite a while. That hasn't changed, and your real issue is the slow DNS
Doing an strace should tell you which DNS server gets queried, but it's
probably your router acting as a DNS forwarder; and the real issue becomes
why your router takes several seconds to return a DNS response.