Skip to main content

Changing hostname to active account

Comments

3 comments

  • bunglehaze
    Just as a chance to get ahead of things. I setup my active business domain with ns1.domain & ns2.domain and pointed it to the dedicated IP address I have on the server. Hopefully if I get a bit of advice on here that reassures me it's relatively simple I can switch it all around with no downtime as the new ns1&ns2 are propagated. Am I making a mountain out of a molehill and is there a dead simple way to just change the domains over to lose the not required hostname account for the vps?
    0
  • cPanelLauren
    Hello, The server actually needs to have a separate hostname from any domain on it. The hostname also doesn't need it's own account. Technically you could have something like domain.com as your hosted domain/account and then add server.domain.com as the hostname - in this case you wouldn't need two separate domain names. The hostname should always be in the format sub.example.com though and shouldn't exist as anything else on the server. As far as changing the nameservers go:
    Just as a chance to get ahead of things. I setup my active business domain with ns1.domain & ns2.domain and pointed it to the dedicated IP address I have on the server. Hopefully if I get a bit of advice on here that reassures me it's relatively simple I can switch it all around with no downtime as the new ns1&ns2 are propagated.

    If you've created new nameservers, registered them with your registrar and pointed them to the server as long as they're propagated you should be able to modify the nameservers of your domain to the new ones, allow time for propagation again, then once that's complete remove the old ones entirely. This should not cause any downtime.
    0
  • bunglehaze
    Hello, The server actually needs to have a separate hostname from any domain on it. The hostname also doesn't need it's own account. Technically you could have something like domain.com as your hosted domain/account and then add server.domain.com as the hostname - in this case you wouldn't need two separate domain names. The hostname should always be in the format sub.example.com though and shouldn't exist as anything else on the server. As far as changing the nameservers go: If you've created new nameservers, registered them with your registrar and pointed them to the server as long as they're propagated you should be able to modify the nameservers of your domain to the new ones, allow time for propagation again, then once that's complete remove the old ones entirely. This should not cause any downtime.

    Thanks Lauren, so you are saying that if my active domain is domain.com I can just change the hostname as host.domain.com and delete the account in the backend that is from my original hostname of olddomain.com. I see a few settings for the venet and IP for the server being different to the dedicated ones for the active domain so i can just change venet 0:0 to 0:1 and the IP to the dedicated IP and it should just keep running fine? I assume that my mail settings (currently mail.olddomain.com would just then change to mail.domain.com I must admit, i am incredibly frustrated with the server hosts who are refusing the assist. it's been a number of years since I had my own servers and I paid for managed service to avoid needing to do things like this.
    0

Please sign in to leave a comment.