another hostname question

[-Anti-]

Firstly, this is a general question.
Please don't make any changes to my account based on this question...

I have a personal VPS account, with two domains using its name servers.
One domain is used only for the hostname; it does not have a cpanel account.
The other domain is my website with a cpanel account.
The reason I set it up like that was because when I used the same domain for hostname and a cpanel account, the hostname prefix would appear as a subdomain in cpanel, which I thought was quite 'messy' and undesirable.

OK, so now I want to purchase an VPS account for the school I work at. They will only have one domain. I am wondering whether I should:

· leave the hostname as vpsxxx.eukhost.com
· utilise the domain that I have already used for my personal account
· register an additonal separate domain, and use that.

Thanks for any advice.

[Rsync]

Firstly, this is a general question.
Please don't make any changes to my account based on this question...

I have a personal VPS account, with two domains using its name servers.
One domain is used only for the hostname; it does not have a cpanel account.
The other domain is my website with a cpanel account.
The reason I set it up like that was because when I used the same domain for hostname and a cpanel account, the hostname prefix would appear as a subdomain in cpanel, which I thought was quite 'messy' and undesirable.

To setup a hostname, there is no need to add a separate subdomain from cPanel.
You can just directly add "A" record for the hostname from WHM >> DNS Functions >> Edit DNS Zone option, OR directly add an another DNS record for your hostname from WHM >> DNS Functions >> Add a DNS Zone
Adding A record for hostname will not display as a subdomain in cPanel of that account.

OK, so now I want to purchase an VPS account for the school I work at. They will only have one domain. I am wondering whether I should:

. leave the hostname as vpsxxx.eukhost.com
· utilise the domain that I have already used for my personal account
· register an additonal separate domain, and use that.

If you don't want to use your domain for hostname, then you can use our provided nameserver for the hostname.

[-Anti-]

Thanks for your reply.

> To setup a hostname, there is no need to add a separate subdomain from cPanel

I didn't set-up the subdomain - it occured automatically.
I set hostname to server.mydomain.com then created a cpanel account using
mydomain.com, and in the root, the subdomain 'server' was automatically generated.
I didn't like that, so I then used separate domains for the hostname and my website,
which works fine.

> If you don't want to use your domain for hostname, then you can use our
> provided nameserver for the hostname.

That would be the simplest solution. Is there any disadvantage to that, apart from
having vpsxxx.eukhost.com used as the server in email headers?

Thanks.

[Scott]

Hi Phillip,

If you use nameserver as a hostname then email headers will show nameserver instead of domain name. There will be no other disadvantage.
It is better to use your own domain name in hostname. I can see that you setup it correctly.

[ccmpj806]

I'm experiencing the same problem.

Set up an A record for the hostname of my server and it appears as a subdomain in cPanel, pointing to a default document root and being unable to redirect via cPanel.

Would the solution be to create a separate zone file for just the server hostname?

Thanks,
Jason.

[Rsync]

I'm experiencing the same problem.

Set up an A record for the hostname of my server and it appears as a subdomain in cPanel, pointing to a default document root and being unable to redirect via cPanel.

Would the solution be to create a separate zone file for just the server hostname?

Thanks,
Jason.

Hello Jason,

We have set the hostname for your VPS from the main hardware node and also added the necessary DNS entry for your hostname on your VPS. Once the hostname DNS entries propagated you will not receive any "A" record hostname missing entry error.

[ccmpj806]

Hi Rsync,

Thanks for that. The new subdomain still shows up in the cpanel with the doc root being /usr/local/apache/htdocs.

Well, as that particular cPanel would only be seen by me, I've decided it's pretty much a non-issue, so I've just put in an index.php file that redirects to the holding page that I've created for my main domain, rather than the default apache holding page found at the defined root.

Had a quick peek at the apache conf file, but decided the above was quicker rather than figure out how to maintain my changes when the conf is regenerated by cPanel.

Again, thanks for the quick response. This is one of the main reasons I'm with Eukhost.

Cheers,
Jason.

[artesea]

The new subdomain still shows up in the cpanel with the doc root being /usr/local/apache/htdocs.

Well, as that particular cPanel would only be seen by me, I've decided it's pretty much a non-issue, so I've just put in an index.php file that redirects to the holding page that I've created for my main domain, rather than the default apache holding page found at the defined root.

Noticed the same issue on mine, however if I create an index.php file it just gives a 500 error.

[Rsync]

Hello Ryan,

I have set the hostname for your VPS from the main hardware node and added the necessary DNS entry.
Also I am able to view login URL for "WHM" and "cPanel" on your hostname. If you have configured any other page then provide us the exact path of that uploaded page, so that we can make the necessary change for you.
Please check after clearing the cache of your local browser.

[Rock]

Noticed the same issue on mine, however if I create an index.php file it just gives a 500 error.

500 error represents Internal server error, which mostly occurs due to incorrect user permissions.. correcting them would fix the problem

[artesea]

I've renamed the files.
index.html is the old default cPanel file.
index.php is currently just a simple html file but with the .php extention

ls -l shows:

-rw-r--r--   1 root root 3474 Apr 11 11:05 index.html
-rw-r--r--   1 root root  318 Jun  8 18:49 index.php

I'm just looking at having a simple holding page for the VPS hostname, and was hoping to use php to check for a cookie, which would then display a different page to me.

[Rock]

I've renamed the files.
index.html is the old default cPanel file.
index.php is currently just a simple html file but with the .php extention

ls -l shows:

-rw-r--r--   1 root root 3474 Apr 11 11:05 index.html
-rw-r--r--   1 root root  318 Jun  8 18:49 index.php

I'm just looking at having a simple holding page for the VPS hostname, and was hoping to use php to check for a cookie, which would then display a different page to me.

The permissions need to be nobody.nobody for the index.php:

-rw-r--r-- 1 nobody nobody 318 Jun 8 18:49 index.php

Please clear the browser cache & check the hostname

[artesea]

Many thanks for the speedy fix Rock

[Rsync]

I've renamed the files.
index.html is the old default cPanel file.
index.php is currently just a simple html file but with the .php extention

ls -l shows:

-rw-r--r--   1 root root 3474 Apr 11 11:05 index.html
-rw-r--r--   1 root root  318 Jun  8 18:49 index.php

I'm just looking at having a simple holding page for the VPS hostname, and was hoping to use php to check for a cookie, which would then display a different page to me.

I have changed the ownership of index.php to nobody and moved index.html to index.html_BK. Now you will not get internal server error on your index.php page.

[Rock]

Many thanks for the speedy fix Rock

You're welcome.. Ahh it was Rsync who fixed this, thanks to him as well..

[Rsync]

You're welcome.. Ahh it was Rsync who fixed this, thanks to him as well..

Thanks Rock, It's our pleasure to help our clients