Migration complete....kinda...

Greebo

Greebo

N9017H - C172M (1976)
Joined
Feb 11, 2005
Messages
10,976
Location
Baltimore, MD
Display Name
Display name:
Retired Evil Overlord
Ok, I goofed.

I checked the TTLs, I THOUGHT for all of the domains, but I must have missed the .com (of course, the main one) because its ttl was set for 1 week. The others were all set for 1/2 or 1 hour.

So for a while, at least until jesse or flyne can help me point calls to the old server to the new one, use the pilotsofamerica.net url for the time being.

G
 
Chuck,

An easy work around might be an automatic redirect at the old site

something like

Code: 
<html>
<head>
<META HTTP-EQUIV="Refresh" CONTENT="5; URL=http://www.pilotsofamerica.net">
</head>
<body>
If your browser does not redirect you automatically click <A HREF="http://www.pilotsofamerica.net"> here.</A>
</body>
</html>
Joe
 
Greebo said:
Ok, I goofed.

I checked the TTLs, I THOUGHT for all of the domains, but I must have missed the .com (of course, the main one) because its ttl was set for 1 week. The others were all set for 1/2 or 1 hour.

So for a while, at least until jesse or flyne can help me point calls to the old server to the new one, use the pilotsofamerica.net url for the time being.

G
Click to expand...


Chuck, replace the VBulletin homepage on the other server with a simple webpage that contains an automatic redirect to here.

I'm out of the office on the laptop at the moment (and I'm not an HTML expert off the top of my head), but I think something like this should work.

<html>
<head>
<meta http-equiv="refresh" content="4; URL=www.pilotsofamerica.net">
</head>
<body>
<p align="center">The page has moved temporarily:</p>
<p align="center">
<a href= "http://www.pilotsofamerica.net">
click here if your are not redirected automatically</a></p>
</body>
</html>
Click to expand...
 
I can do that, but its not as clean as I'd really like. I want .com to be forced to the new IP, not just redirected.
 
Greebo said:
I can do that, but its not as clean as I'd really like. I want .com to be forced to the new IP, not just redirected.
Click to expand...

Understood and agree.

May want to do that in the short term until you get the "force" in place.
 
Greebo said:
I can do that, but its not as clean as I'd really like. I want .com to be forced to the new IP, not just redirected.
Click to expand...

The problem is the TTL (time to live) is a directive that tells people how long to keep the DNS lookup in THEIR cache.

So people will be accessing it locally without hitting the authoritative DNS for up to a week.

Joe
 
Yeah you're right - i'll change the master template to do that now.

If I can get to it - the .com site has frozen up again... figures. ;)
 
Areeda said:
The problem is the TTL (time to live) is a directive that tells people how long to keep the DNS lookup in THEIR cache.

So people will be accessing it locally without hitting the authoritative DNS for up to a week.

Joe
Click to expand...
I know. Jesse or someone mentioned a way to have the vserver receive port 80 requests and forward them to the new IP in the interrim...

But think that may have its own pitfalls.
 
Greebo said:
I know. Jesse or someone mentioned a way to have the vserver receive port 80 requests and forward them to the new IP in the interrim...

But think that may have its own pitfalls.
Click to expand...


You'd really be putting a proxy server in place.... not necessarily an anon proxy, but a proxy nonetheless.

I'm not sure SloDaddy allows proxy functionality, but I'm not sure.

Or just copy some code from one of the online advertising inserts... such as opening a frame with the new site, frame sized to full screen.

Trouble with that is that a SLO server on the proxy/frame host (.com) may not load at all. Releasing/unloading the vB services may free up enough capacity to let it operate, though.
 
Well the redirects are now in place - that should do for now I think.
 
wsuffa said:
You'd really be putting a proxy server in place.... not necessarily an anon proxy, but a proxy nonetheless.
/quote]

No need for a proxy. You would create an iptables rule to route all traffic inbound on port 80 to the new server's ip.
Click to expand...
 
What impact would the old server's regular freezes have on that?
 
Chuck, just do the http redirect on Apache
http://httpd.apache.org/docs/2.1/en/mod/mod_alias.html#redirect


Or the Apache mod_rewrite
http://httpd.apache.org/docs/1.3/mod/mod_alias.html#redirect

You only have to put the .httpd.conf in the web root on the old server. MAKE SURE you do the temporary redirect, AKA 302.

That's only 3 ways to do it and the w3 says to not use the refresh as above,
http://www.w3.org/QA/Tips/reback
but it's only temporary in your case. Enough?


You can change that when the DNS change propogates.
 
Last edited:
You must log in or register to reply here.
Back
Top