Help - Search - Members - Calendar
Full Version: Nameservers correctly set, but site not available?
The Planet Forums > System Administration > Web Hosting
hosting-hub
I have got the nameservers for my site, filedeposit.com, correctly set to ns1.hosting-hub.com and ns2.hosting-hub.com. I have also added this domain in HELM (filedeposit.com).

However, I can't seem to access the site, it says "Cannot find server". On the other hand, I have changed the nameservers for "lifegauge.com" to the same nameservers, and created the domain "lifegauge.com" in HELM, and the site shows "403 Error", which is correct because the folder's empty.

My question is, why is it that I'm unable to access the first site "filedeposit.com", when I can access the second "lifegauge.com"? Both domains have different registrars, if that matters.

I appreciate your help and advice, thanks.
eddy2099
It probably is just a propagation issue. Give it some more time and try again after 24 hours.

I understand that you are from Singapore. Did the trace from here and got the same results as you but when I did it from my server in SM, both shows the forbidden error.
hosting-hub
It's funny why "lifegauge.com" propagonates faster than "filedeposit.com"
eddy2099
There is no clear cut answer here. It could be that when the changes was made on one of the registrar, it propagates the information faster than the other. Because there is a lot of interconnectivity and a lot of servers which needs to be updated and paths to take, there is going to be a lot of possibilities which we should not try to explore or understand.

Both domain names were propagated in the US but some thing causes one to reach Asia a little slower than the other.

Give it another 24 hours and try again.
rabbit994
Well they haven't gotten very far. When I do a reverse lookup on your NS, this is what I get

a.gtld-servers.net dns1.name-services.com. dns2.name-services.com. dns3.name-services.com. dns4.name-services.com. dns5.name-services.com. 146ms

g.gtld-servers.net dns1.name-services.com. dns2.name-services.com. dns3.name-services.com. dns4.name-services.com. dns5.name-services.com. 146ms

h.gtld-servers.net dns1.name-services.com. dns2.name-services.com. dns3.name-services.com. dns4.name-services.com. dns5.name-services.com. 147ms

c.gtld-servers.net dns1.name-services.com. dns2.name-services.com. dns3.name-services.com. dns4.name-services.com. dns5.name-services.com. 147ms

i.gtld-servers.net dns1.name-services.com. dns2.name-services.com. dns3.name-services.com. dns4.name-services.com. dns5.name-services.com. 147ms

b.gtld-servers.net dns1.name-services.com. dns2.name-services.com. dns3.name-services.com. dns4.name-services.com. dns5.name-services.com. 147ms

d.gtld-servers.net dns1.name-services.com. dns2.name-services.com. dns3.name-services.com. dns4.name-services.com. dns5.name-services.com. 281ms

l.gtld-servers.net dns1.name-services.com. dns2.name-services.com. dns3.name-services.com. dns4.name-services.com. dns5.name-services.com. 281ms

f.gtld-servers.net dns1.name-services.com. dns2.name-services.com. dns3.name-services.com. dns4.name-services.com. dns5.name-services.com. 281ms

j.gtld-servers.net dns1.name-services.com. dns2.name-services.com. dns3.name-services.com. dns4.name-services.co
m. dns5.name-services.com. 282ms

k.gtld-servers.net dns1.name-services.com. dns2.name-services.com. dns3.name-services.com. dns4.name-services.co
m. dns5.name-services.com. 282ms

e.gtld-servers.net dns1.name-services.com. dns2.name-services.com. dns3.name-services.com. dns4.name-services.com. dns5.name-services.com. 282ms

m.gtld-servers.net dns1.name-services.com. dns2.name-services.com. dns3.name-services.com. dns4.name-services.com. dns5.name-services.com. 534ms
eddy2099
Both the domain names are working fine now. It was just a matter of propagation.
rabbit994
The bane of dealing with DNS....
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2010 Invision Power Services, Inc.