Is This A cPanel/WHM Bug?

**Poppet25** · #1 (**permalink**) 24-09-2009, 09:24

I keep getting this email message from the server,

"IMPORTANT: Do not ignore this email.
The hostname (*************************) resolves to . It should resolve to xxx.xxx.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
automatically correct this problem by using the ' Add an A entry for your
hostname ' under ' Dns Functions ' in your Web Host Manager"

Every site is working ok, just wondered if it was a bug and if there is a fix for it. This was happening on our old hosts too.

**Scott** · #2 (**permalink**) 24-09-2009, 09:55

Hi,

It is not a bug of cPanel control panel. Cpanel needs fully qualified hostname.

Currently your semi-dedicated server is having default hostname set, which needs to be changed with the actual domain hosted on your semi-dedicated server. Please let me know the domain name you want to use in hostname and will set the proper hostname.

**jennifer** · #3 (**permalink**) 25-09-2009, 06:11

Quote:

Originally Posted by Poppet25

I keep getting this email message from the server,

"IMPORTANT: Do not ignore this email.
The hostname (*************************) resolves to . It should resolve to xxx.xxx.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 automatically correct this problem by using the ' Add an A entry for your hostname ' under ' Dns Functions ' in your Web Host Manager"

Every site is working ok, just wondered if it was a bug and if there is a fix for it. This was happening on our old hosts too.

A newly setup cPanel system may have such a message. I have fixed this for you now and the pop-up is no longer seen.

Please log in to your WHM to see if the message returns. If the pop-up still appears for you, please let me know. Also, if you need the hostname set to a different hostname other than the current one I have set it to, that can be modified right away for you upon request.

Just so you know how this is fixed:

You can resolve this by going to the DNS Functions area on the left menu in WHM and selecting Add an A Entry for your Hostname. It will ask you to confirm the details: press Add entry to do so.

WHM should automatically try to add the relevant A record for your hostname to the DNS zone present on your system.

If you have any questions, feel free to ask

**Poppet25** · #4 (**permalink**) 25-09-2009, 10:05

I'm confused I cannot log into WHM using the web address but I can log in using the ip addy. All the websites appear to be working now, I've done the usual, reboot router/pc, cleared cache etc but it's saying the hostname is what I set it to, that's supposed to be wrong

**jennifer** · #5 (**permalink**) 25-09-2009, 10:55

Should be working for you now, I updated the hostname from the main node.

Let me know how you get on it.

**Poppet25** · #6 (**permalink**) 25-09-2009, 10:57

Thanks Jennifer will do.

**Poppet25** · #7 (**permalink**) 28-09-2009, 19:25

I'm still getting the DNS error thought I'd leave it until things calmed down.

**-Anti-** · #8 (**permalink**) 02-10-2009, 07:55

You may be interested in this thread:

info: hostname errors

I researched this when I kept getting the same error on every new VPS I purchased.
The eukhost staff normally fix it by doing something at node level.
But I found with my newest VPS that I fixed it without needing to contact support.

Note that I only had to perform 'RNDC Fix #1'.

**eukSam** · #9 (**permalink**) 02-10-2009, 08:04

Hello,

When ever we create a new vps, we set a temporary hostname for the vps on node & this temporary hostname does not resolve to any ipaddress due to which WHM keeps giving error regarding the hostname. Once the client provides a domain, we set the hostname for the vps on that domain.

WHM constantly checks the hostname. Though the hostname is set correctly & the named service goes down on the vps, WHM gives the hostname error. In this case you just have to restart the named service.