On Thu, Dec 11, 2008 at 10:10 AM, Ken Schneider
Almost sounds like a routing issue instead of a dns issue. Could you please post the results of route -n?
# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 172.24.0.0 0.0.0.0 255.255.254.0 U 0 0 0 eth3 192.168.0.0 0.0.0.0 255.255.240.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 If it were a routing issue, then the dig command would have just as many problems with resolving names as any other app. I can sit there hitting Retry in yast while it's consistenly failing to resolve download.opensuse.org, yet have another window open and dig is resolving that name just fine. And just to make sure I wasn't completely insane and/or overlooking a typo, I made sure I was using the same name server configured in resolv.conf by doing: dig +short download.opensuse.org @`awk '/^nameserver/ {print $2}' /etc/resolv.conf | head -1` -- Andy Harrison public key: 0x67518262 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org