--- Eric Hines
We had a similar problem with ComCast a bit over a year ago, and it was their DNS servers (which they denied, but that's another story). However, that problem was getting initial name resolution so
we could go anywhere at all. We pointed our router/firewall at other, non-ComCast DNS servers (we're using 4dot2dot2dot2, 64dot81dot45dot2, and 64dot81dot79dot2), and we've had no problem since.
Many thanks to all who made suggestions, much appreciated. In the end the problem was that the Actiontec DSL modem's DNS proxy server was lying. The effect was that the modem told the DHCP client to use 192.168.0.1 (the modem) and another address for DNS. It reported itself first on the list. For some reason, the web browsers (tried Firefox, Mozilla, and Konqueror) all went to the modem for DNS lookup. Sometimes this was successful, but most of the time, it reported 1.0.0.0 for any requested address. Clearly, when pointed to that address the browsers were bound to fail. Curiously, other parts of the system (ping, nslookup, traceroute etc.) all got the right address. I didn't determine if this was because they abandoned the modem when it was so obviously lying, or because somehow they went to the second server anyway. I _thought_ that DNS lookup was a system call, and they should all get the same response. Any thoughts? Anyway, I reconfigured DHCP to ignore the offered DNS server list, and simply hard-wired the two Qwest servers in to /etc/resolv.conf. The system now works smoothly and my friend is happily learning her way round Linux instead of Windows (yeah! chalk one up to the good guys :) Again, thanks for all comments, Cheers, Simon "You can tell whether a man is clever by his answers. You can tell whether a man is wise by his questions." Naguib Mahfouz __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com