In a previous thread, http://forums.cpanel.net/showthread.php?t=64647, a user has a problem with DNS clustering which results in the nameserver returning "Can't list domain <domain name>: BAD ERROR VALUE." - I'm also having this problem.
After following Chirpy's suggestions in the above referenced post:
I am still having the same problem with *only* my NS2 returning BAD ERROR VALUE when I look anything up against it.It could be that the zones have not propagated properly to the new server. Check in /var/named/ on the new server and see if it does indeed have all the expected .db files, also check /etc/named.conf for the same. If not, login to one of the cluster servers that is correct and run WHM > Synchronize DNS Records > Sync All. This can take some time to complete and use considerable server resources on all DNS cluster members, but when complete all the members ought to have the same zone file information within /etc/named.conf and /var/named/
As far as I can tell, my NS1 (cPanel/WHM Server) is setup correctly; the /etc/named.conf file contains proper statements for all the domains (zone files) I am hosting. For example:
On my clustered (cPanel's DNS ONLY) server, which is my NS2, there is no reference to any of my zone files in /etc/named.conf - however, all of the zone files DO EXIST in /var/named.Code:zone "mydomain.com" { type master; file "/var/named/mydomain.com.db"; };
I even tried a clean setup from scratch and get the same results. I've tried syncing everything. Any suggestions?
I am running CentOS 5.2 for both instances. All firewalls have also been removed for this NS2 until I can find out what is causing the problem.
Thanks,
-Sean



LinkBack URL
About LinkBacks
Reply With Quote






