A whois query will not identify a problem in your dns configuration. To check if dns is returning an IP address correctly, you should use the "dig" command in the format: $ dig www.yourdomain.com
If you see an an answer such as: ;; ANSWER SECTION: www.redhat.com. 300 IN A 66.187.232.56 and your IP address is correct, then you know dns is working. Another common way to test dns is to "ping" the server as in: $ ping www.yourdomain.com If you get a response such as $ ping www.wikkedskye.com ping: unknown host www.wikkedskye.com you know dns or some other part of name resolution is not working. Another common problem for situations like this is that your web server (I'm assuming you are using apache) has a misconfiguration in the virtual web site section. If you can provide more specific data with your question, you'll get better answers. For example, if you feel comfortable sharing your domain name, others can determine if dns is working or not. mjb On Sat, 2003-03-29 at 17:56, Wikked Skye wrote: > I have been trying with this and reading articles with this for four > days now, and I am stumped. I have checked everything, ports are open, > firewall is set okay. I can get to my website by using the ip, but not > with the www address. Everything is pointed correctly. I have checked > with WhoIs and everything seems to be set correctly. I have checked > with my DSL provider and all ports are open. The only thing I can > figure is that it must be something in this BIND configuration and the > way I have it set up. Is there any documentation that can explain this > better? Or anyone out there that might know more than me, since I am > just a beginner anyway. > > Thanks, > Kelly -- Mark Johnson-Barbier
signature.asc
Description: This is a digitally signed message part
