Two domains point to the same location?
I asked this before, but got caught up in setting up the new business.
The new business is moving along real fast now, and it's time to setup the domains.
I've registered both, let's call them example.com and example.net
I also have my first domain, domain.com.
I wanted example.com and example.net ran under my wife's name, instead of being ran by me, like domain.com is.
I want it so example.com and example.net point to the same location on the VPS.
I created an account for my wife and created the domain example.com. The registar has the nameservers setup as ns1.domain.com and ns2.domain.com.
1) Should the two new domains have their own ns1 and ns2 DNS entry?
2) How do I go about creating the second example.net domain, and having it point to the same physical directory that example.com points to? I tried creating an add-on domain, but that appears to just create a sub-domain, which isn't what we want.
All three domains are currently running on the same VPS.
Thanks!
-
Hi @Spork Schivago I set a personal reminder to remind me to request an update from you on Monday April 23rd to determine if the update resolved the issue. It's been my pleasure helping you and I'm so happy that between the Techincal analysts and I we were able to help get your issues resolved. Thank you so much! 0 -
Hi @Spork Schivago I had a notification to remind you to update today but it looks like v70 will not be in CURRENT until May 7th so if you'd like I'll set another reminder to update and let us know if that resolves the issues you were having with CPANEL-17258 0 -
Yes please, please set another reminder to remind me. Sorry, been busy setting up the business and forgot all about this. Thank you. 0 -
Hi @Spork Schivago That's quite alright, I set one for next week already and I'll update here when it goes off! Thank you! 0 -
Hi @Spork Schivago I just wanted to let you know that a few minutes ago 70.0.32 was published to the RELEASE tier so please update when you're able to and let us know if the issue is now resolved. Thanks! 0 -
Thanks cPanelLauren. I have updated but the issue remains. On top of that, now the various cPanel services (whm, webmail, etc) are receiving a self-signed certificate. I tried picking the AutoSSL certificate, which only lists webmail, whm, and cpanel (none of the other cPanel services) but that failed. And my hostname isn't listed in there either. Very frustrating and time consuming trying to fix this mess. Any ideas? 0 -
Hi @Spork Schivago Could you please re-open Ticket ID 9443133 so that we can take a look and hopefully resolve the issue for you. I am sorry that the issue is still occurring. Thanks! 0 -
Yes, I will reopen it. Thank you for giving me the ticket number and helping. 0 -
Turns out AutoSSL does not support proxy subdomains for parked domains because cPanel felt it was a waste of SSL certificates, yet they still provide www aliases for subdomains which makes no sense to me. I understand having the www alias for the main domain, but the subdomain's? That's just a waste of SSL certificates! People shouldn't be able to go to places like www.hostname.domain.com, just hostname.domain.com. There should at least be an option to turn it off or on. I was using the .local Apache templates and manually checking if the domain was my main domain, and if it was, then adding the www alias, but if it wasn't, then not doing so. If there was a variable for main domain versus the entire domain name, including the subdomain, it'd make it a lot easier! Then we could just have an if statement that checks if the subdomain is equal to the domain variable, if it is, write the alias, if not, don't write the alias, but I could never find the proper variable, which kinda sucked. Worked fine with one domain, but with three, caused issues, so I had to remove it and now have a bunch of unneeded www.subdomain.domain.com SSL certificates.... Anyway, the level 3 tech was able to fix the problem by making it not a parked domain, setting up the proper redirects, etc. SSL certs are now being generated for all three domains and we're good to go. I don't know the password for the username he created, but I don't need to, because we'll never log into that account. I should probably change the shell to noshell or something, just to be safe. Thanks! 0 -
Hi @Spork Schivago I'm really happy to hear that the analyst was able to get the issue handled for you, even if it's not the initial way you had intended. You shouldn't need to know the password for the user in order to change it through WHM in the event you need access to the account. If you don't plan on accessing via SSH I would suggest changing the user's shell to noshell as well. Thanks! 0
Please sign in to leave a comment.
Comments
70 comments