WHM no-ip nameservers - Impossible to configure DNS correctly


Nov 1, 2011
cPanel Access Level
Root Administrator

I'm having some trouble my vas change ip address and now when i try to updated my dns parameters in my registrar configuration it fails

For my domain i have setup correctly the ns1 and ns2 A records + ns1 and ns2 ns records

here is the configuration page :

but when i check the name servers configured i have no-ip


The problem is sometimes i have the following email :

MPORTANT: Do not ignore this email.

Your hostname (domain.com) could not be resolved to an IP
address. This means that /etc/hosts is not set up correctly, and/or
there is no dns entry for domain.com. Please be sure that
the contents of /etc/hosts are configured correctly, and also that
there is a correct 'A' entry for the domain in the zone file.

Some or all of these problems can be caused by /etc/resolv.conf
being setup incorrectly. Please check that 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' option under 'Dns Functions' in
your Web Host Manager.
The content of my /etc/resolv.conf file is


I have updated cpanel to the latest version using upcp command

Can someone help me ?


Staff member
Apr 11, 2011
Hello :)

The functionality of the "Nameserver IPs" page is for visual purposes only. It is a report, and not a page meant to configure any aspect of DNS. It reports the nameservers used by DNS zones on the server, as well as a count of the the number of zones that use a given nameserver. The important entries on the cPanel server are the "A" records that you have added for your name servers. Thus, as long as you have registered these name servers to the matching IP addresses at the domain registrar, then no further DNS configuration is required. The "Nameserver IPs" page can include cached data, so you can safely ignore any mentions of "No IP" on that page as it may take some time before it updates.

As for the hostname, make sure the "A" record for your hostname is added at the DNS host of the primary domain name associated with it. You can run the IPcheck script manually to see if the issue persists via:

/scripts/ipcheck --verbose
Thank you.