We are starting the server transfer, RationalWiki is now locked down. We need to sync the file system and the database to the new server and then do some magic and then see if it all worked out.
It will take a few hours to a few days depending on the internet gods till rationalwiki.org points to the new server.
However, rationalbeta.com should be pointing to the new server for everyone and the ip address 173.255.233.133 should also default to RationalWiki. I will announce everywhere when the server move is complete and normal operations can resume at the new site, and I hear tell that there is also going to be some celebrating at the old site.
Subscribe to:
Post Comments (Atom)
{{crickets}}
ReplyDeleteAh, so yet more burning of the evidence of your cyber terrorism and wanton vandalism of an education project.
ReplyDeleteAll made possible possible by a huge 'donation' courtesy of Mother Russia. Where the wiki writes you.
ReplyDeleteTrent, we'll need the IP address of the old location (your IP address) in order to play in the old sandbox after the move is complete.
ReplyDeleteBut that is far less important than "best of luck with the debugging magic!"
Lol at whoever is pretending to be Rob.
You already know the IP address, at least your computer knows. just type "ping rationalwiki.org" into the command prompt and it should print it out. Or use http://ip-lookup.net/domain.php
ReplyDeleteOOPS:
ReplyDeleteNo IP address found for the domain 'http://rationalwiki.org'
(no DNS answer).
That site is stupid, it works if you drop the http:// part.
ReplyDelete72.38.27.54 for the lazy but I think it points the /var/www atm
ReplyDeletegive a man a fish etc.
ReplyDeleteThat is one philosophy the other is the crack dealer philosophy of increasing dependence
ReplyDeleteNo Internet Gods needed.
ReplyDeleteDNS is a database with a distributed cache. Whenever you ask a DNS question (like "What's the address of rationalwiki.blogspot.com so I can connect to it?") the answer includes a validity period or Time To Live, ("It's 127.0.0.1 and that answer is good for 18 hours, 7 minute and 4 seconds").
When you change something, people won't "see" the change so long as somewhere between them and you is a cache which believes the old value is valid. Only when the time runs out do their systems ask again.
So BEFORE you change something, you need to ensure that your DNS records have only very short TTLs, say 30 minutes. Once you've made the change, these short TTLs will quickly expire, and everything works. You can then bump them up again to the old value.
The More You Know
Ok, we're almost there...
ReplyDelete