Web Hosting Talk : Web Hosting Main Forums : Web Hosting : average time for DNS propagation?

[Fayte]

Hello,

How long should it take for a domain name to resolve to the proper server?

My host switched from Alabanza to VDI. I've been reading a few posts about VDI vs. Alabanza, but back to my original topic...

Due to the switch, my account was placed on a new server with a new IP.

I updated my nameservers on Monday. The new nameservers appear when I do a whois from rs.internic.net. But when I do a traceroute on the new IP, it resolves to the server's info and not to my domain name. If I do a traceroute on my old IP, it still resolves to the domain name.

I placed a trouble ticket with my host asking why my domain name wasn't pointing to the new IP. The guy said I should allow it another day to propagate through the 'Net. Hmph, yeah right. Easy, lazy answer.

I'm wondering...
- isn't this my host's responsibility? Shouldn't they delete my domain name from the old IP and add it to the new one?
- is this truly something that will occur once the propagation is "complete"?
- whether the registrar can do something about this?

Can anyone provide some insight on this? Thanks!

[SmartHosting]

Dear Fayte,

It may take up to 72 hours for the changes to propagate. If it will not begin working for you in 72 hours, then you can inform your webhost that the propagation period is over and that it still doesn't work.

Please, keep in mind, that in rare occasions it may take longer, but within the U.S. the maximum waiting period is 72 hours and with an 24 hours or less on an average basis.

[Fayte]

Thanks SmartHosting,

I guess I'm just frustrated because it's never before taken this long for changes to take effect on any of my domains. Not that I'd expected instant results or anything, but I figured 24-72 hours would be a reasonable period and I'm currently hovering at the 72 hour mark [this does make me sound impatient, doesn't it? ]. I'm hoping it will right itself over the weekend.

[m6.net]

Some time it could be problem of your local dns cage. make sure you referesh the memories of your dns cage or try other computer to check the domain.

Note: You may be aware of it.

[Fayte]

I ran traceroutes from yahoo.com, network-tools.com, and from my home and work connections and none of them could find my domain, so I'm thinking this is something my host screwed up.

I submitted another trouble ticket today and haven't heard back from them yet. In the meantime I switched my nameservers back to the old values.

I think it might be time to change hosts!

[ksstudio]

For a Top Level Domain Name, usually it only takes 24-72 hours for the domain name server changes to propagate.

For a country domain name it might take longer period to resolved. I got some bad experience with one of the country domain registrar ( MyNic - registra of domain.com.my ) where i have to print out a confirmation form to chop, sign and fax back to them and wait another 4-5 days to propagate, and some more it replies that my name server is not recogniced (actually it is fine with other top level domain registra) and ask me to resubmit new name server.

[avara]

I once registered a domain name, and it had propagated and was working only 4 hours later. Why is it that when you register a new domain name, it usually propagates much faster than when you change an exisiting one to new DNS servers?

[cactus]

Originally posted by ksstudio
For a country domain name it might take longer period to resolved. I got some bad experience with one of the country domain registrar ( MyNic - registra of domain.com.my ) where i have to print out a confirmation form to chop, sign and fax back to them and wait another 4-5 days to propagate, and some more it replies that my name server is not recogniced (actually it is fine with other top level domain registra) and ask me to resubmit new name server

Yes, our country have very strict rules and if you want to register a domain for example abc.com.my you will have to submit your application with your business registration documents to support it through the dealers who have their servers at CyberJaya(NOC) where all the servers are housed at. After the domain name is approve by the governing body(MyNic) then only can you then host you domain on a server.

For any changes/update to your records(for example nameservers) you have to go back to your Host and they will submit the neccessary documents to the authorities for approval before it can be updated.

As you can see it's difficult to register a domain even for us locals and many don't want to go through all that bureaucracy that is really a hassle where you can anytime connect to the Internet, go to one of those Domain Registrars, and get a "Domain.com" within ten minutes either for personal or business and look for a "Web Hosting of your choice and get it hosted all within an hour compared to the former where it take days and all the red tapes and expensive cost to register a domain.

Please don't quote me as the above info was passed on to me by a friend who's in the Web Hosting business and owns a few servers locally.

[thewitt]

Just to add a data point here - for what it's worth.

I just moved two domains last month. They both took 10 days before traffic stopped hitting the old site. The bulk of the DNS servers were updated within 72-96 hours, but there were still some coming in to the old address on day 10.

On one of these domains, I could see the new site from work, but my ISP access at home still had the old site for three more days. I finally called their tech support and wouldn't you know it, the DNS change went though literally while I was waiting on hold to talk to the support tech...

-t

[Fayte]

Originally posted by avara
I once registered a domain name, and it had propagated and was working only 4 hours later. Why is it that when you register a new domain name, it usually propagates much faster than when you change an exisiting one to new DNS servers?

I was wondering about that too!

[SmartHosting]

Hi Fayte,

There are many different ways to see if your host, itself, has configured your DNS properly - to at least resolve within their own network. If it doesn't resolve within their network (which, when DNS changes are made, usually have instantaneous effect) - then you shouldn't expect the rest of the world to be able to resolve it.

One way is to connect to you telnet and run nslookup, from the outside we can do the same, but we would need to know your webhost, your domain name or the nameservers that your domain name is registered under. Of course, there are many other network/DNS tools that can be used for this purpose that may yield more specific results - which we will not get into as nslookup will suffice in this case.

[Fayte]

Originally posted by SmartHosting
One way is to connect to you telnet and run nslookup, from the outside we can do the same, but we would need to know your webhost, your domain name or the nameservers that your domain name is registered under. Of course, there are many other network/DNS tools that can be used for this purpose that may yield more specific results - which we will not get into as nslookup will suffice in this case.

I'd appreciate it if you could run nslookup for me!

The domain is riotous.net, my host is oc12host (oc12host.com). The old nameservers were ns1.oc12host.com & ns2.oc12host.com. The new nameservers are ns1.oc12host.net and ns2.oc12host.net. However, I went to dotster last night and switched back to my old nameservers, so now the name could end up pointing anywhere (except where I want it to, which is to the new server).

[SmartHosting]

Hi Fayte,

At oc12host's primary DNS, your domain name resolves to the IP address 64.176.55.60. However, any other of your webhost's nameservers will not resolve your domain name - especially the 2 last ones.

Please, contact your webhost. It seems to us as a misconfiguration on their end.

[Fayte]

I had a feeling that they had something to do with this, since they're the ones who put the accounts on the servers. I pretty much wanted to tell them "this is YOUR responsibility, host, you fix it!" but I had to check with knowledgeable folks - you guys - before I threw the blame at them.

The last time I contacted them they blamed it on the Internet - "the changes need to propagate" yadda yadda.

Thanks SmartHosting for confirming it!!