Hi Richard,
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).
user-pc.3.home
to the 127.0.0.1 and ::1 entry lines in your /etc/hosts file.
Thanks for the hint, I'll give it a try tomorrow.
Thanks, Clemens
Clemens Eisserer writes:
Hi Richard,
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 /etc/resolv.conf
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 response.
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.
Hi Sam,
The app tries a DNS lookup for "user-pc". The domain gets appended from /etc/resolv.conf
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 response.
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.
Actually, for looking up my own hostname no DNS query should be needed at all. I've just checked - even in case it really is a configuration issue within the network - Windows7 just copes fine with it
So I wonder, shouldn't the DNS code in glibc simply detect the lookup in this case is localhost (as Windows DNS implementation does obiously)?
Regards, Clemens
-
Clemens Eisserer -
Sam Varshavchik