Mailinglist Archive: opensuse-bugs (14006 mails)

[bugzilla_noreply@xxxxxxxxxx]

https://bugzilla.novell.com/show_bug.cgi?id=383336

User mmeeks@xxxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=383336#c25





--- Comment #25 from Michael Meeks <mmeeks@xxxxxxxxxx>  2008-04-30 11:05:48 MST 
---
Ludwig wrote:
> Sounds like a problem with your name server. It should pretty fast
> determine that it cannot resolve the host and return with an error.

Well - it seems to me if the hostname is looked up; it is not at all clear that
'linux' is not a root domain name, or some magic thingit - and the name server
does it's best.

FWIW - you can point at the DNS server being mis-configured as much as you like
- but it's a fairly default Netgear DSL router / hub thing - and
(unfortunately) it appears to expose next-to-no DNS settings - ie. it's not
just me [ and the thing runs Linux - so the manufacturers must be at least
slightly clueful ;-].

> That would simulate the case where your dhcp server hands out invalid
> name servers. Of course that will cause timeouts.

sure - but it appears to be the same timeout - and you see the issue I hope: we
do a -ton- of IP lookups in common applications; sudo eg.

> yast does set some domain by default, IIRC 'site. You can see it in
> /etc/HOSTNAME or /etc/defaultdomain

my /etc/HOSTNAME says "linux.site" my /etc/defaultdomain is empty however.

> That's with your hostname added to /etc/hosts.

oh - quite right [ at least now I try again ] getent gives me no output, and it
takes 21.5 seconds to timeout & get back to me.

Adding a 'search foo' to my /etc/resolv.conf (or a 'site' instead of foo or
whatever) has ~0 effect on the problem.

But then - ping 'linux.site' or ping 'linux.foo' is also just as slow - so, not
sure what we can achieve there.


-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.