[email protected] [~]# /scripts/adddns server.xxxxxx***********
Add Dns 1.0 ...
Warning, this only adds dns to the local server ...
If this server is not the dns master, this will not work
Enter ip? xx.xx.xx.xx
Setup server.x*********** OK [email protected] [~]# rndc reload [email protected] [~]# /etc/init.d/named restart
Stopping named: [ OK ]
Starting named: [ OK ] [email protected] [~]#
after command try to login WHM get same error...
The server was unable to lookup an an A entry for its hostname (server.xxx***********). This is generally because the entry was never added. However this could also be the result of your nameserver(s) being down. If you would like to attempt to automaticlly add the entry,
Is the hostname for a domain hosted on the server? e.g. server.domain.com, where domain.com is hosted on the server (with the server's nameservers?), if not, then that could be your problem.
In SSH, check to see if you can resolve the server's hostname;
# host server.domain.com
MediaLayer, LLC - www.medialayer.comLearn how we can make your website load faster, translating to better conversion rates for your business!
The pioneers of optimized web hosting, featuring LiteSpeed Web Server & SSD Storage - Celebrating 10 Years in Business
Seems the server hostname is not resolving and hence the issue.
You may check this using "host server.domain.com " in ssh
The domain.com will be resolving to some other ip and server.domain.com is not set up with respect to that dns.
You may try adding "nameserver 127.0.01" in /etc/resolv.conf so that the hostname will be resolving locally with respect to the server and we can get rid of the warning message.