On Tuesday 21 March 2006 01:11, Andrew J. Kopciuch wrote: > By "resolving" you mean does not find the correct IP address for that > domain yes?
By Resolving, I mean "name not found". Doing a dig against my DNS server (192.168.0.10) works fine - the server can resolve the name. But my workstation cannot - with the resolv.conf pointing to my DNS server. There is no DHCP or anything else that *should* be changing the resolv file dynamically. Thanks for the dig tip though. I had previously tried a nslookup against the registered name servers for the domain (whois from cira), and used those results to prove the target webserver was running. So I knew it was something with my system then, not theirs.... Any other tips? (other than leaving the secondary name server in resolv.conf)? Shawn _______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
