Moving website from VDS to webhosting

[JackLL]

I have a problem that I'm very confused about.

I have a website hosted at uolostlands.com, which currently resides on a VDS. I have an A record set up with Amazon Web Services which points here. I have no problem with hosting it on the VDS, everything works perfectly.

I spent the time getting all my databases and the website set up on webhosting, which is hosted at new.uolostlands.com.

Once everything was ready, I thought it would be easy to just switch the domain uolostlands.com from the VDS over to the webhosting, but this hasn't proved easy for me.

I can not seem to get uolostlands.com to point to the webhosting. new.uolostlands.com has no problem pointing there by setting the Name Servers in AWS for "new.uolostlands.com" to NS1.NFOSERVERS.COM/NS2.NFOSERVERS.COM and setting up the folders in the control panel.

However when I do the exact same thing with uolostlands.com (set the name servers to NS1/NS2 NFOservers and set in control panel), it never resolves. The control panel acts as if it should resolve (I get no errors), but it doesn't work. I was told by support that I need to wait 48 hours but this doesn't make sense to me when any other NS server I set (test.uolostlands.com, vent.uolostlands.com, etc) resolves in a matter of minutes. Even http://www.uolostlands.com will resolve in minutes, just not uolostlands.com.

I hope support are correct but I think there could well be miscommunication and I'm not getting heard. Can anyone shed light on what else I could be doing wrong.

[JackLL]

After reading up more I think I understand why there is the 48h hour delay. I noticed the TTL on the Name Servers are set to 48 hours which makes more sense to me why these are so much slower to update than the new Name Servers I set for the subdomains.

For now I have left the A record pointing to my current VDS and changed the name servers to the relevant NFOServer hosting. Fingers crossed I understand correctly and when the name servers are next checked then uolostlands.com will swap over to the hosting here.

[Vanderburg]

10 years ago, is was quite normal to expect to wait 48 hours. Now, that's given as a "safe" number. It's usually much faster than that. You can usually get it to resolve for yourself much faster than that (sometimes in just a couple minutes) by clearing your DNS cache and using faster DNS servers. I use Google's DNS servers, which are 8.8.8.8 and 8.8.4.4, though OpenDNS and a few others are quite fast, too.

Though, even though you can speed it up for yourself, you shouldn't expect your users to be able to do to the same. You should expect your users, as a rule, to see it after it happens automatically, not through a manual effort.