I believe I have this issue resolved. Ultimately, it seems to be
related to the nameservers from my ISP or some sort of interaction
between my router and DNS. Perhaps someone could shed some more light
on this if they have solved a similar issue.
Here is what I tried:
1. I edited resolv.conf, trying each name server by itself. Of the
three name servers, #1 and #2 worked by themselves and I was able to
install some zypper packages, while #3 had failures where it couldn't
resolv a hostname. Enabling #1 and #2 together unexpectedly also
resulted in a failure. I wouldn't consider any of my tests objective,
as I don't know how to correctly flush DNS and reload the
configuration; I did "/etc/init.d/network restart" between tests.
2. From searching the net, I came across a post that claimed that the
Linksys WRT54G router actually runs a nameserver service and may be
used as such. Setting my nameserver to the router's IP seems to work
well for my configuration. My router is version 8.0 with firmware
8.00.5. This leads me to believe my problem may be some strange
Linux/router/DNS interaction. I'm really unsure... if this setup
works, I probably will not invest more debugging time in the immediate
future.
Here is the link to the thread that lead me to set my router as my nameserver:
http://creativekarma.com/ee.php/weblog/comments/slow_dns_response_on_linux_with_wrt54g_router/Lastly, can someone else confirm that the green network activity light
stays solidly on when no network activity is occurring?
-Mick
--
To unsubscribe, e-mail:
opensuse-ppc+unsubscribe@...
For additional commands, e-mail:
opensuse-ppc+help@...
