Wow Posted December 14, 2011 Share Posted December 14, 2011 We are currently underway to upgrade our server hardware configuration. We will be moving from our current single dedicated server to two scalable dedicated servers - for web and database. This will significantly reduce our risk of slowdowns during peak times during major weather events and provide an easier platform to scale our hardware resources up or down depending on what we need. We should be fully migrated by some time tomorrow at the latest. This will involve an IP address change so if you are unable to reach the site for a short time, the cause is probably DNS servers still propagating the new IP address. Thanks for your support as we continue to grow. Link to comment Share on other sites More sharing options...
weatherwiz Posted December 14, 2011 Share Posted December 14, 2011 We are currently underway to upgrade our server hardware configuration. We will be moving from our current single dedicated server to two scalable dedicated servers - for web and database. This will should significantly reduce our risk of slowdowns during peak times during major weather events and provide an easier platform to scale our hardware resources up or down depending on what we need. We should be fully migrated by some time tomorrow at the latest. This will involve an IP address change so if you are unable to reach the site for a short time, the cause is probably DNS servers still propagating the new IP address. Thanks for your support as we continue to grow. If DNS becomes an issue what would we be able to do? Or will it fix itself? Link to comment Share on other sites More sharing options...
Kmlwx Posted December 14, 2011 Share Posted December 14, 2011 If DNS becomes an issue what would we be able to do? Or will it fix itself? As he said - it takes times to propagate. So as all the various DNS options (Verizon, OpenDNS etc) all get the new IP address it will be resolved. OpenDNS has worked best for me. Most people use the DNS that their ISP gives them (ex: mine was set to Verizon's by default). Link to comment Share on other sites More sharing options...
Wow Posted December 14, 2011 Author Share Posted December 14, 2011 If DNS becomes an issue what would we be able to do? Or will it fix itself? It will fix itself. We will adjust some settings to try to make the down time as short as possible but it all depends on the DNS server your computer is set to ping. If you are able to, you can change your DNS settings to ping a different server but for most, just waiting it out is the best advice. It shouldn't be long. Link to comment Share on other sites More sharing options...
weatherwiz Posted December 14, 2011 Share Posted December 14, 2011 Thanks! Link to comment Share on other sites More sharing options...
wxmx Posted December 14, 2011 Share Posted December 14, 2011 If the old server is still around, you can redirect directly to the IP (new server would have to serve the forums using the IP, of course)...or better, there's probably time to do it, create a new subdomain (say www1.americanwx.com) with the new IP address if it's available, and redirect all accesses to the old server to it, that would probably work since it's a new subdomain (no TTL and since theres no previous record, they defer to your NS directly, unless there's some lengthy cache) and there's more time to propagate. Just some suggestions to Wow... though the probable small downtime for some might not deserve to deviate his efforts making the new server functional. Link to comment Share on other sites More sharing options...
KokomoWX Posted December 14, 2011 Share Posted December 14, 2011 Hopefully the DNS admin has adjusted the TTL to a very low number to speed up DNS changes. Link to comment Share on other sites More sharing options...
Ginx snewx Posted December 14, 2011 Share Posted December 14, 2011 Thank all you guys for your hard work. Link to comment Share on other sites More sharing options...
Kevin Druff Posted December 14, 2011 Share Posted December 14, 2011 If the old server is still around, you can redirect directly to the IP (new server would have to serve the forums using the IP, of course)...or better, there's probably time to do it, create a new subdomain (say www1.americanwx.com) with the new IP address if it's available, and redirect all accesses to the old server to it, that would probably work since it's a new subdomain (no TTL and since theres no previous record, they defer to your NS directly, unless there's some lengthy cache) and there's more time to propagate. Just some suggestions to Wow... though the probable small downtime for some might not deserve to deviate his efforts making the new server functional. I've done this before. A new sub domain pointing to the new IP address with a 302 redirect in the .htaccess of the old one. Link to comment Share on other sites More sharing options...
wxmx Posted December 14, 2011 Share Posted December 14, 2011 I've done this before. A new sub domain pointing to the new IP address with a 302 redirect in the .htaccess of the old one. Yep, not that hard and very effective. But I understand there are priorities, and resources are not plenty. It's obviously just a suggestion. Link to comment Share on other sites More sharing options...
Wow Posted December 14, 2011 Author Share Posted December 14, 2011 Yep, not that hard and very effective. But I understand there are priorities, and resources are not plenty. It's obviously just a suggestion. It's a good one. We might use that. Link to comment Share on other sites More sharing options...
DaculaWeather Posted December 15, 2011 Share Posted December 15, 2011 No need to change DNS just to redirect. Just add a redirect statement to an index.html file in the root of the BB. Make it instant. <meta HTTP-EQUIV="REFRESH" content="0; url=http://www.yournewserver.com/index.html"> Link to comment Share on other sites More sharing options...
wxmx Posted December 15, 2011 Share Posted December 15, 2011 No need to change DNS just to redirect. Just add a redirect statement to an index.html file in the root of the BB. Make it instant. <meta HTTP-EQUIV="REFRESH" content="0; url=http://www.yournewserver.com/index.html"> That would not work, since "www.yournewserver.com" is www.americanwx.com, but for some people it'll resolve to the old server...that will cause a redirect to itself, which will cause a loop...it's a DNS issue. Link to comment Share on other sites More sharing options...
DaculaWeather Posted December 15, 2011 Share Posted December 15, 2011 No it won't. It's a different IP address for the new servers. Both the old and new servers will be available, same DNS just different IP's. At least as far as DNS servers around the internet are concerned. If one DNS continues to see the old server, you'll go there and get redirected to the new IP address. That will work until all DNS servers have been updated and then you'll only go to the new address. Link to comment Share on other sites More sharing options...
wxmx Posted December 15, 2011 Share Posted December 15, 2011 That's the issue...some people will be resolving to the old server, even if the NS is pointing to a new one. You suggested to redirect to "www.yournewserver.com" ... those people will resolve to the old server. Ie. www.americanwx.com -> old IP (10.1.1.1) change www.americanwx.com to point to new IP (20.1.1.1) Some ISP DNS servers are slow to update....some people type www.americanwx.com->resolves to 10.1.1.1 loads your html with meta refresh redirect .... points to "www.yournewserver.com" which is "www.americanwx.com"->resolves to 10.1.1.1 loads your html with meta refresh redirect .... points to "www.yournewserver.com" which is "www.americanwx.com"->resolves to 10.1.1.1 loads your html with meta refresh redirect .... points to "www.yournewserver.com" which is "www.americanwx.com"->resolves to 10.1.1.1 loads your html with meta refresh redirect .... points to "www.yournewserver.com" which is "www.americanwx.com"->resolves to 10.1.1.1 if you suggested to point to the new IP directly instead of "www.yournewserver.com", then it would work...that was my solution 1) ... but it's better to use a new subdomain, IMO... no ugly IPs in your address bars. Link to comment Share on other sites More sharing options...
Kevin Druff Posted December 15, 2011 Share Posted December 15, 2011 Once you're resolved to the old IP, you'll always go to the old IP until the TTL expires. In other words, Dacula, your suggestion would results in an endless loop. If you used a new domain or sub-domain, your meta refresh would work. However, it's more appropriate to use a 302 Temporary redirect in your server config. This lets Google Bots know the content has moved temporarily and doesn't affect their algorithms. Your way could affect SEO scores, etc. Link to comment Share on other sites More sharing options...
DaculaWeather Posted December 15, 2011 Share Posted December 15, 2011 Once you're resolved to the old IP, you'll always go to the old IP until the TTL expires. In other words, Dacula, your suggestion would results in an endless loop. If you used a new domain or sub-domain, your meta refresh would work. However, it's more appropriate to use a 302 Temporary redirect in your server config. This lets Google Bots know the content has moved temporarily and doesn't affect their algorithms. Your way could affect SEO scores, etc. Not if you redirect to an ip. Your 2nd part was going to be my other suggestion. Link to comment Share on other sites More sharing options...
Wow Posted December 17, 2011 Author Share Posted December 17, 2011 Welcome to the new server! Link to comment Share on other sites More sharing options...
Ginx snewx Posted December 17, 2011 Share Posted December 17, 2011 Nice job, that was quick, thanks. Link to comment Share on other sites More sharing options...
#NoPoles Posted December 17, 2011 Share Posted December 17, 2011 so, i can't attach pics...keep getting an error message, and no, they are not too big... Link to comment Share on other sites More sharing options...
TheTrials Posted December 17, 2011 Share Posted December 17, 2011 Any suggestions for getting on? Can access from phone not home computer Link to comment Share on other sites More sharing options...
eekuasepinniW Posted December 17, 2011 Share Posted December 17, 2011 so, i can't attach pics...keep getting an error message, and no, they are not too big... Noted. Any suggestions for getting on? Can access from phone not home computer Just wait. Link to comment Share on other sites More sharing options...
ELCwx Posted December 17, 2011 Share Posted December 17, 2011 No problems at all. Very smooth for me. Thanks to the tech crew for the effort. Link to comment Share on other sites More sharing options...
eekuasepinniW Posted December 17, 2011 Share Posted December 17, 2011 Upload issue is resolved. Link to comment Share on other sites More sharing options...
Baroclinic Zone Posted December 17, 2011 Share Posted December 17, 2011 Working nicely Scott. That was pretty seamless and fast. Link to comment Share on other sites More sharing options...
Chicago WX Posted December 17, 2011 Share Posted December 17, 2011 I'm sure you guys will get it fixed in due time, but I can't access Alan's model page or the AMEX WRF...from the drop down links above. Otherwise, good to go. Thanks. Link to comment Share on other sites More sharing options...
#NoPoles Posted December 17, 2011 Share Posted December 17, 2011 Upload issue is resolved. thanks!!! Link to comment Share on other sites More sharing options...
ELCwx Posted December 18, 2011 Share Posted December 18, 2011 Earlier tonight the board started switching my skin to subscription without me doing anything. I couldn't see most posts because of that. That problem has stopped but now I can't see the information to the left of the posts (avatar, post count, location, etc...). It shows up for a split second when I start up but then it disappears, and the posts get scruntched down. I am using Firefox on Macbook Pro. Oddly, when I switched to Safari everything was back to normal. Any idea whatup? Link to comment Share on other sites More sharing options...
Wow Posted December 18, 2011 Author Share Posted December 18, 2011 Earlier tonight the board started switching my skin to subscription without me doing anything. I couldn't see most posts because of that. That problem has stopped but now I can't see the information to the left of the posts (avatar, post count, location, etc...). It shows up for a split second when I start up but then it disappears, and the posts get scruntched down. I am using Firefox on Macbook Pro. Oddly, when I switched to Safari everything was back to normal. Any idea whatup? If it's working fine on another browser then it may be a browser problem. Try deleting your cache for the browser. Link to comment Share on other sites More sharing options...
ELCwx Posted December 18, 2011 Share Posted December 18, 2011 If it's working fine on another browser then it may be a browser problem. Try deleting your cache for the browser. It back to working normally again. I had to delete the log in cookie and log in manually again but that seems to have fixed it. Thanks. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.