I’ve switch the server that this website is hosted on, from the old 1995-era machine sitting in my basement at home, to the mildly more sleek 2000-era machine sitting above my head here at the new data centre. The move should be seamless and painless. Please alert me to any irregularities. If you’re reading this post, then you’re seeing the new server.
About This Blog
I am Peter Rukavina and this is my blog. I am a writer, letterpress printer, and a curious person.
To learn more about me, read my /now, look at my bio, read presentations and speeches I’ve written, or get in touch (peter@rukavina.net is the quickest way). You can subscribe to an RSS feed of posts, an RSS feed of comments, or receive a daily digests of posts by email.
Comments
Saw this post mid-afternoon,
Saw this post mid-afternoon, then it was gone off and all posts for last day or so down, now back up just now.
Looks like still filtering -
Looks like still filtering - you might want to say that this is what is happening.
Sorry, Peter, I am
Sorry, Peter, I am understanding from Nate that the matter is one of propagation to the new URL. Just to let you know, then, that the old does not flip over here in Kingston but the new one can be seen directly.
Why not setup an a name to
Why not setup an a name to point to the new server from the old server????? Then everyone views the same page during propagation :P
Remember, John that I may
Remember, John that I may well have restated the situation erroneously being an utter bone-head in such stuff. I just wanted to make sure the QSL to engineering was properly reflecting reception.
I wouldn’t go as far as
I wouldn’t go as far as calling ya a bone-head, thats a bit harsh. The computer I am on right now is showing the proper site with the new dns, however last time I checked my home computers were showing the old server.
reinvented.net not showing
reinvented.net not showing beyond “Hydrogen’s Dirty Little Secret”. Also, no links to Discuss.
www.reinvented.net working fine.
Yep, he has his A name record
Yep, he has his A name record pointed to his old ip through eastlink 24.222.26.154 as opposed to his new one through ISN 198.167.161.50
Seriously, you guys are
Seriously, you guys are taking this way, way too seriously.
Seriously? ;)
Seriously? ;)
Last may I had to move a
Last may I had to move a cluster of 32+ servers from one IDC in Sunnyvale CA to another in Boston MA, all without more than an hour of downtime (at 3am, ugh). Aside from totally sucking it made my Kung-Fu much stronger. One good tip any time you plan on moving ip’s is to crank you’re DNS TTL down to 5 mins 24-48 hours before you move. This will increase the load on your resolvers but allows you to make a change and have the change propigate in 5-10 minutes instead of 6-12 hours. I’ve used this trick a few times quite successfully.
Cody, Nice tip!
Cody, Nice tip!
What? I am being too serious?
What? I am being too serious??? Nooo my life is ruined!
Add new comment