Couple of hosting questions

[UKSBD]

I have a reseller account using WHM and cPanel with about 30 accounts in it.

All but one accounts are just 1 account for 1 domain, but one of them is 1 account with 2 sub domains.

domainA.co is main account with domainB.co and domainC.co as subdomains in that account

Question is;
If I don't renew domain registration of domainA.co will domainB.co and domainC.co still work?

Next question
When originally setting up the hosting you use a domain to create the main account, can you let this domain registration lapse or is it required for the whole account to work?

 

[ukwebhosting]

Hi

Yes subdomains will work even if the main cPanel domain is not registered.

The main domain you could also let lapse as you could use for example

https://serverhostname.com/whm or https://ipaddress:2087 (you will get an ssl error using IP)

You could also use domainb.co or c with /whm or /cpanel or even :2087 for whm and :2086 for cPanel

 

[ServWise]

Assuming domainB and domainC are not simply redirecting to domainA then not renewing domainA won't affect B or C, even if they alias domainA they should still work.

 

[UKSBD]

Thanks both.

I was pretty sure that was the case, but wanted to check before letting them lapse

 

[martin_shl]

The only issue I could see with that is if someone else registers that domain and starts using it. I don't understand the nuts and bolts fully, but I once had an issue moving a domain to my host as it must have previously been there. They had to fix the other account so I could add it to mine.

One thing my host introduced me to and I've carried on doing is using a made up (and very unlikely to ever be used e.g. "randomstring-mydomain.co.uk" ) domain as the domain for the cPanel account and then the domain under it is added as an add-on domain. It makes it a bit easier to manage and another advantage is you're not constrained to putting the website in "public_html"

 

[ServWise]

The only issue I could see with that is if someone else registers that domain and starts using it. I don't understand the nuts and bolts fully, but I once had an issue moving a domain to my host as it must have previously been there. They had to fix the other account so I could add it to mine.

One thing my host introduced me to and I've carried on doing is using a made up (and very unlikely to ever be used e.g. "randomstring-mydomain.co.uk" ) domain as the domain for the cPanel account and then the domain under it is added as an add-on domain. It makes it a bit easier to manage and another advantage is you're not constrained to putting the website in "public_html"

Yep, It is also possible changing the plans main domain to a random domain at a later date.

 

[UKSBD]

I don't understand the nuts and bolts fully, but I once had an issue moving a domain to my host as it must have previously been there. They had to fix the other account so I could add it to mine.

I've had similar

Had a domain set up in my hosting, decided to move it to another host so deleted from the 1st one.

Year or so later I wanted to move it back to the original host, tried to create it but got an error

Account Creation Status: failed
(XID xex497) A DNS entry for “demoxxxxxxdemo.co” already exists. You must remove this DNS entry from this server or all servers in the DNS cluster to proceed.

Although I thought I had previously deleted it, there is obviously a setting the host had to delete too.

 

[HostXNow]

I've had similar

Had a domain set up in my hosting, decided to move it to another host so deleted from the 1st one.

Year or so later I wanted to move it back to the original host, tried to create it but got an error

Account Creation Status: failed
(XID xex497) A DNS entry for “demoxxxxxxdemo.co” already exists. You must remove this DNS entry from this server or all servers in the DNS cluster to proceed.

Although I thought I had previously deleted it, there is obviously a setting the host had to delete too.

This issue can occur when a web hosting service using cPanel is set up with a cPanel DNS cluster. When an account is terminated, both the account or domain and its associated DNS zone(s) should be removed from the server and the cPanel DNS-only cluster. However, there are times when the DNS zone is not removed as it should be. This is more of a problem with cPanel itself than with the web host. If DNS zone(s) are left behind, the web host will need to manually remove them from the cPanel DNS-only cluster before the cPanel account or domain can be recreated.