Take the 2-minute tour ×
Server Fault is a question and answer site for professional system and network administrators. It's 100% free, no registration required.

I have registered a new domain. I want to use it with my server. I have a static IP for my server. Using my registrar control panel I have added an A record for my domain.com with value IP of my server. When I look it up with using http://www.hcidata.info/host2ip.htm page to find the IP address which domain.com matches I can get the result as my IP adress but when I browse the domain.com it does not respond. What is the problem, how can i get rid of it?

share|improve this question
    
I've just tried dig domain.com, host domain.com, and nslookup domain.com will get you started. all of them failed with no server by timeout –  dirtybit May 12 '11 at 20:24

3 Answers 3

If you've just created this domain, please wait 24-48 hours before starting any troubleshooting. This is to allow the new entries in the root nameservers to be entered and picked up. If you've had this domain for longer than 24-48 hours and you are still having trouble, post the domain name here and we'll sort it out for you straight away.

share|improve this answer

If you're able to look up the domain and get your IP address on a third-party website, it may not be a DNS issue. You should confirm resolution using dig, host, or nslookup.

If you created your DNS record without a www, make sure you are not trying to browse to www.domain.com.

Finally, is your web server running? If you browse to the IP address, does it work?

share|improve this answer
    
Web server is running when i browse it with using IP address everything is fine. www issue is not the case i am sure about it. How can i confirm resolution using dig, host, nslookup? Could you explain a little bit more, please? –  dirtybit May 12 '11 at 20:05
    
Do I need to do anything at the server side after specifying DNS records? –  dirtybit May 12 '11 at 20:06
    
dig domain.com, host domain.com, or nslookup domain.com will get you started. –  Cakemox May 12 '11 at 20:09
    
all of them failed with no server by timeout –  dirtybit May 12 '11 at 20:12
    
Try dig +trace domain.com to see exactly where it is failing. –  Cakemox May 13 '11 at 8:11

I'm going to take a stab and say that you probably just set this up. DNS takes time to propagate globally, anywhere from 24-72 hours. If it's still doing it at that point, then check back in with us.

share|improve this answer
    
Thanks.. so why can the web page i've mentioned above return the IP address? I really wonder this is why i am asking. –  dirtybit May 12 '11 at 19:45
    
It just depends on what DNS server it's querying. DNS servers cache both positive and negative responses for hostnames, and store them for various amounts of time. This is why it takes a generous amount of time for everything to even out. If you're truly curious and want to know more about DNS, pick up this book and give it a read. It has everything you could want to know about DNS in it. –  Holocryptic May 12 '11 at 19:49
    
Actually, you generally do not need to wait that long for propagation of a new domain. A change to an existing DNS record may take a while to be fully switched due to TTL issues, but new records are generally quite fast. Gone are the days of new .com domains taking up to 24 hours to be created due to zone generation only happening twice daily. –  Cakemox May 12 '11 at 19:50
    
@Cakemox you're probably right, but it's definitely not instantaneous either. –  Holocryptic May 12 '11 at 19:52
    
@holo they changed the Root DNS servers refresh interval from 24 hours to ~2 hours a while back. –  Zypher May 12 '11 at 20:57

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.