Skip to main content

Need to reassign domain name to public_html folder if possible

Comments

9 comments

  • cPRex Jurassic Moderator
    Hey there! For question one, you'll want to pick a hostname that does resolve, but that you don't plan to use for any web traffic. A lot of people choose something like "host.domain.com" so they can easily add an A record to an existing DNS zone so the hostname resolves. For question two, there isn't a way to do that. You'd just want to change the hostname and create a new account for that website. For question three, yes, although if you do this too many times the license may lock due to our security checks. If that happens, just contact our Customer Service team and we can get that lock removed. To clarify, you'll want all your web data in the /home/username/public_html directory for each unique cPanel account you create. Any other directories are not web-accessible and not designed to host websites on a cPanel server.
    0
  • petenorris
    cPRex; Thank you for responding. I appreciate the information. Regarding question one: a). would I need to register a domain name to use for the hostname that does resolve but I don't plan to use for web traffic? b). would the WHM root domain name be used only for nameservers like ns1.host.domain.com, ns2 host.domain.com, etc or something else? c). could I use host.domain.com for the WHM root account and put domain.com in the /home/username/public_html directory for web access? I want to eventually offer web hosting to customers using the WHMCS platform. Technical support at WHMCS tells me that I need two servers, i). one server for the web hosting purchase or commerce website and ii). one server upon which the customers' websites would reside. I would like to use the host.domain.com for the nameservers and the domain.com name for the web hosting commerce site. Question 4: Could the WHM root account discussed in this thread be used for i). or ii). above or would I need a different configuration altogether? Thanks.
    0
  • cPRex Jurassic Moderator
    A - Not necessarily. I can be a domain name you're already using. For example, you could have domain.com as your website, and host.domain.com as the hostname, and that is perfectly fine. B - The nameservers can be whatever you want and aren't linked to any domain or the hostname. C - Exactly that :D There is no "WHM root account" - you have your root username and password for the server, which also lets you access WHM, but that isn't related to any web hosting domain. Does that help clear things up?
    0
  • petenorris
    Yes, that does clear things up. :) Just one more question for this thread. I think I need to start all over again with a new Linode VPS. Question 5-a). Can I just overwrite my current WHM license account with the newly created Linode VPS or do I need to first delete the account and assign the newly created Linode to the current cPanel license? Question 5-b). If I need to delete instead of overwrite how would be the best way to delete? Thank you for your assistance.
    0
  • cPRex Jurassic Moderator
    The license doesn't necessarily "know" it's applied to a certain server. You'll just delete the current server, create the new one, and then update the license IP address using these steps:
    0
  • petenorris
    Wow! Great. I am going to keep this thread bookmarked or subscribed for future reference. Thanks again.
    0
  • cPRex Jurassic Moderator
    Sure thing!
    0
  • petenorris
    Hello Forum. I have got myself confused again. I deleted the previous Linode (discussed above) and established a new Linode. The new Linode has a different IP address. The nameservers for the new Linode assigned for cPanel do not resolve. Those nameservers are: ns1.cprapid.com ns2.cprapid.com ns3.cprapid.com ns4.cprapid.com
    0
  • cPRex Jurassic Moderator
    6a - yes, the cprapid nameservers are just placeholders so your temporary hostname resolves. They won't do anything for actual domain names. 6b - you should change them there as well so the proper entries get added to future DNS zones you create, but remember that nameservers are created and handled at the registrar level too.
    0

Please sign in to leave a comment.