Server Switch - Question

[sdfontanini]

Okay we did a server switch today and some of the members still can't access the page, while others are able to. I've been told that this switch takes time to get out to some people, is that really the case or am I missing something here?

[Lats]

Yes, DNS can take some time to propagate.

What you can do is go to your old server and force a redirect to your new ip.

[sdfontanini]

Yes, DNS can take some time to propagate.

What you can do is go to your old server and force a redirect to your new ip.

Okay I was wondering what the deal was.

how do I go about forcin the old server to redirect to the new IP?

[Lats]

A meta redirect is quite simple...

http://www.w3schools.com/html/html_meta.asp

[sdfontanini]

A meta redirect is quite simple...

http://www.w3schools.com/html/html_meta.asp

Guess I'll look into this tonight.

Eventually will all my customer's be able to get back on to the site. Lets say I give it another few days or so?

[sdfontanini]

<meta name="OLD IP ADDRESS???" content="????">

I would put this into my header or what? I'm a little confused

[Lats]

A meta redirect in the header...
http://www.w3schools.com/html/tryit.asp?filename=tryhtml_redirect

[bigwater]

This will not prevent re-direction back to the old site however as config.php specifies an URL. The only practical solution is to wait for DNS to propogate.

There is the option of temporarily changing the URL of the site in config.php on the new server to an absolute address like http://xxx.xxx.xxx.xxx/~username which will prevent it from redirecting back to the old server for visitors who don't have updated DNS information yet, but it gets old after the first half dozen or so times you do it, because you have to go back and change it back to an URL after full propogation to keep things "pretty".

The easiest way is to just close the board on the old server with a "temorarily closed for maintenance" message, open it on the new server, change your nameservers at the registrar, and wait it out. Once a user's DNS information becomes current, the board will appear open. Until then it'll appear closed.

My experience with over 25 server moves for people is that it never takes more than a couple of days to get world wide propogation... at least I've never had a client complain about it outside of a couple of days.

[Lats]

For your next server move, best check out the procedure of lowering ttls' - that speeds up propagation.

[bigwater]

Yes, lowering ttl works well for short hops to the server, and works well when you can control the ttl settings on the nameserver, but it isn't always possible with clients who don't run their own nameservers (use their provider's nameservers) or on nameservers that aren't RFC compliant.

However you can't control every nameserver on the internet, and if a nameserver depends on caching it's nameserver data from another nameserver before it gets to your client, propogation delays can occur simply due to the timing on the updating of the caches between the various servers in the chain.

Usually they propogate very quickly for servers close by, as within the same continent, but I have had a couple of times where I've moved clients to servers in Houston, and their clients in Amsterdam took a couple of days to see the new server, whereas their clients in Atlanta saw it within a half an hour.

[lostguy]

I dont have problem change/move to new server ... All i do is get new host first and contact them what your situation ..they will help u move your site/forum for u if they support it ...and then they will ask your cpanel / whm panel password for transfer .

To be honest i just moved new host a week ago and i didnt feel Anything ! My Host really good at it .

www.eukhost.com (http://www.eukhost.com)

lg