I've always run the server on "host.example.com" and just left "example.com" alone (the default construction page comes up). Now I'm thinking I want to use "example.com" to promote the business and increase my visibility, but running a website, and all the apps that will come with it, as the Admin user doesn't seem like a safe idea. What would be the safe approach to using the domain name to host a website/services? Should I create a normal user and assign "example.com" to them, but leave "host.example.com" assigned to the Admin user (I assume that's possible)?
Running a public website using the server Domain Name?
- Thread starter TomJones
- Start date
Richard G
Verified User
If you create a seperate dns entry for host.example.com not under admin user but under DNS administration, then you can leave that as is.
And then you could create a new user and assign example.com to him in his account under domain administration.
So in that way it should be possible yes.
It's not needed but if you want it because of more safety in case the accounts get hacked or something then you could do it that way. Or at least should be possible I guess.
And then you could create a new user and assign example.com to him in his account under domain administration.
So in that way it should be possible yes.
It's not needed but if you want it because of more safety in case the accounts get hacked or something then you could do it that way. Or at least should be possible I guess.
Richard G
Verified User
Just comes into mind. Do you also have the nameservers under that domain like ns1.example.com and ns2.example.com?
If yes, then I would not use just a user for the domain but create a reseller account for it so these will keep working like should be.
If yes, then I would not use just a user for the domain but create a reseller account for it so these will keep working like should be.
Thanks for your feedback Richard. Your first post makes sense; I could be using Laravel apps for CRM, etc., so a standard user would help me sleep at night.
I do have those name servers currently, so you are recommending creating a reseller account and creating the user under that reseller? I'm not clear on what the benefit of the reseller account would be. What problems would I be facing if I didn't create a reseller to add the user under?
I do have those name servers currently, so you are recommending creating a reseller account and creating the user under that reseller? I'm not clear on what the benefit of the reseller account would be. What problems would I be facing if I didn't create a reseller to add the user under?
Richard G
Verified User
Yes, because normally users do not have nameservers and in the past I've seen odd issues when nameservers were under a user account.
Might not happen anymore. But still... normally users do not have own nameservers.
I don't know if you create users under admin or if there are no other users. But under a reseller you can create users which then automatically get the correct nameservers too. You can't create users under a user.
And I'm not sure if you create them under admin, if the correct nameservers are used because that domain is not owned by admin anymore.
I could be wrong, but I always take care with these things no odd things can happen and I'm on the safe site.
However if you think it's not necessary, ofcourse feel free to do as you see fit.