The Big Move

Some of my hosting packages are coming up on their renewal dates. I decided a few weeks ago that I would buy a VPS (Virtual Private Server) from my hosting company and move my sites on to that. I consider myself a little above the curve as far as technology goes, but I’m far from a super-hacker network nerd. This is only day one of trying to get it all set up, so I’m not too worried yet, but I fear I might have gotten myself in over my head.

I own three hosted accounts through iPower that I administer through their vDeck program, including this one. I’m not going to mess with those just yet until I successfully set up a less important site.

This is my first attempt at moving a site onto my new VPS:

  1. “Unlock” the domain (, an owned but not hosted domain, empty)
  2. Add Name Servers to that domain ( &
  3. Update the domain to use those new Name Servers
  4. “Lock” the domain
  5. Set up the domain in Plesk (a program that administers my VPS)
  6. Cross fingers that the domain will now resolve to the correct place on my new server
  7. Wait impatiently
  8. If it works, then hopefully FTP will resolve to the same place and I’ll be able to log in and upload my files.

I understand that I can use those same name servers for all of my sites. I’m not sure how that works but that’s what I heard. If anyone out there has experience with this type of thing and has any input, or would be willing to answer some questions, contact me through the email link below. I’m a bit concerned that this is a stupid security risk, that is, telling people what sites I own, on what hosting company, running what software, and where my name servers are. Is it?

2 responses to “The Big Move”

  1. richard says:

    Yeah, I don’t think any of that is a stupid security risk. Anyone who is determined can get most, if not all of that info through WHOIS or pulling up a 404 page on your site. What’s important is how secure the server itself is, as well as the security of the apps you’re running on it.

    I didn’t know you had your own nameservers. Are they virtual? I’ve always used nameservers that belonged to my hosting company.

  2. Chris Coyier says:

    The only reason I’m running a Name Server is because I have to in order to get all my domain names to resolove to my new server. I found it pretty damn complicated, and I didn’t even have to mess with the nuts and bolts of it at all. I’ve had friends bitch and bitch about their DNS servers at work and I don’t want any part of it.

    I’m not sure if my Name Servers are vitual, I don’t think so though. They route to my server which is virtual.

    Maybe setting up a web server was Jamairquoi’s inspiration for Virtual Insanity.

Leave a Reply

Your email address will not be published.