WHM Hostname Confusion!!!

[Gr8-Ideas]

Hi All,

I have just purchased a VPS Rage - cPanel / WHM package. Only thing is I have not been exposed to WHM with my other VPS / hosting accounts (have used Plesk or just cPanel on its own).

When I registered I applied for a new domain name, lets call it "mynewdomain.com". this has been registered and is propogated, "ns1. / ns2." but it is also the hostname of the server - "server.mynewdomain.com". With my previous VPS account the hostname was "VPS[IP].myotherhost.com" so I never had this to deal with.

From WHM manual:

NOTE: Your hostname should be a Fully Qualified Domain Name that will not be used elsewhere on the server. You should never set your hostname to an name that is already used (www, ftp, mail, etc) or to the name of an account on the server (domain.com - Get online with a domain name and web hosting). This means that your hostname should never be a domain name and especially not the name of your domain!!

So if I read this correctly my plan to add the mynewdomain.com as an account cannot be done??
I should have registered the VPS account with another domain name that I dont intend to use in production?? i.e. "mynewserver.com"

To add to the confusion I recieve a mail from cpanel@server.mynewdomain.com

IMPORTANT: Do not ignore this email.
The hostname (server.mynewdomain.com) resolves to . It should resolve to 208.79.xxx.xxx. Please be sure to correct /etc/hosts as well as the 'A' entry in zone file for the domain.

Some are all of these problems can be caused by
/etc/resolv.conf being setup incorrectly. Please check this file if you
believe everything else is correct.

You may be able to
automaticly correct this problem by using the ' Add an A entry for your
hostname ' under ' Dns Functions ' in your Web Host Manager

/etc/hosts is fine | /etc/resolv.conf looks fine

When I "Add an A entry for your hostname" from the WHM panel it tells me the A entry is already there.

So can one of the WHM gurus out there explain how to:

1. get mynewdomain.com into a usuable account, its actually for a client
2. change the hostname so that it never conflicts with any previous or future domain names and resolves correctly

Many thanks in Advance.

Rob

[lnxcode]

Originally Posted by Gr8-Ideas

Hi All,

I have just purchased a VPS Rage - cPanel / WHM package. Only thing is I have not been exposed to WHM with my other VPS / hosting accounts (have used Plesk or just cPanel on its own).

When I registered I applied for a new domain name, lets call it "mynewdomain.com". this has been registered and is propogated, "ns1. / ns2." but it is also the hostname of the server - "server.mynewdomain.com". With my previous VPS account the hostname was "VPS[IP].myotherhost.com" so I never had this to deal with.

From WHM manual:

So if I read this correctly my plan to add the mynewdomain.com as an account cannot be done??
I should have registered the VPS account with another domain name that I dont intend to use in production?? i.e. "mynewserver.com"

To add to the confusion I recieve a mail from cpanel@server.mynewdomain.com

/etc/hosts is fine | /etc/resolv.conf looks fine

When I "Add an A entry for your hostname" from the WHM panel it tells me the A entry is already there.

So can one of the WHM gurus out there explain how to:

1. get mynewdomain.com into a usuable account, its actually for a client
2. change the hostname so that it never conflicts with any previous or future domain names and resolves correctly

Many thanks in Advance.

Rob

Hey - Welcome to the HostICan Forum!

1. Hostnames -

This doesn't matter, so you can / should leave it like it was already set for you as it will be the best working conifg. - I would suggest its exactly how its configured since this wont affect you that much anyways.

2. Adding a new cPanel account

This is an easy fix, all you need to do is go to >> Account Information >> Account Functions >> Create a new account

Domain: mynewdomain.com

Fill in the username / password

All will work fine. The reason why the hostname is set to server.mynewdomain.com is because you're very unlikely to use that subdomain / name in your configs and thus there wont be any clashes.

Happy Christmas! - Hope the above helps

[Gr8-Ideas]

Originally Posted by lnxcode

Hey - Welcome to the HostICan Forum!

1. Hostnames -

This doesn't matter, so you can / should leave it like it was already set for you as it will be the best working conifg. - I would suggest its exactly how its configured since this wont affect you that much anyways.

2. Adding a new cPanel account

This is an easy fix, all you need to do is go to >> Account Information >> Account Functions >> Create a new account

Domain: mynewdomain.com

Fill in the username / password

All will work fine. The reason why the hostname is set to server.mynewdomain.com is because you're very unlikely to use that subdomain / name in your configs and thus there wont be any clashes.

Happy Christmas! - Hope the above helps

Hi Denis,

I have been distracted by the holidays and clients, so not had the chance to fully implement a complete production environment yet.

So I added the account all good, whilst attempting the cPanel proxy issue (other post). I came across this error when service httpd restart was issued.

VirtualHost XXX.XXX.XX.XXX:0 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results

Here is the virtualhost section of my httpd.conf: 1 Server 1 Account.

# DO NOT EDIT. AUTOMATICALLY GENERATED
NameVirtualHost XXX.XXX.XX.XXX:80



ServerName server.mynewdomain.com
DocumentRoot /usr/local/apache/htdocs



ServerName mynewdomain.com
ServerAlias mynewdomain.com
DocumentRoot /home/myuser/public_html
ServerAdmin webmaster@mynewdomain.com
## User myuser # Needed for Cpanel::ApacheConf

suPHP_UserGroup myuser myuser


SuexecUserGroup myuser myuser

CustomLog /usr/local/apache/domlogs/mynewdomain.com-bytes_log "%{%s}t %I .\n%{%s}t %O ."
CustomLog /usr/local/apache/domlogs/mynewdomain.com combined
ScriptAlias /cgi-bin/ /home/myuser/public_html/cgi-bin/

Include "/usr/local/apache/conf/includes/post_virtualhost_global.conf"
Include "/usr/local/apache/conf/includes/post_virtualhost_2.conf"

Is this now not an error from having both the nameserver and a virtualhost configured together? Is this a known error from WHM? Can it simply be ignored??

Rob

P.S. When accessing mynewdomain.com the usual

Apache is working on your cPanel® and WHM™ Server

green screen does not appear??

Thanks a million for all your help

[Gr8-Ideas]

Bump! Anyone before I start harassing support

TIA

[lnxcode]

Hey man.

This is normal for all cPanel VPS's they all come back with:

VirtualHost XXX.XXX.XX.XXX:0 -- mixing * ports and non-* ports with a NameVirtualHost address is not supported, proceeding with undefined results

So feel free just to ignore it. Sorry for my delay in response... I've been trying to keep my head above water

[Gr8-Ideas]

Thanks Denis. Good luck with the swimming.

Rob - The Scottish Kid !!!