之前一直遇到这个问题
[root@mgmt3 ~]host node01 ;; connection timed out; trying next origin ;; connection timed out; no servers could be reached [root@mgmt3 ~]nslookup node01 ;; connection timed out; trying next origin [root@mgmt3 ~]dig @192.168.10.254 node01 ; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.10.rc1.el6 <<>> @192.168.10.254 node01 ; (1 server found) ;; global options: +cmd ;; connection timed out; no servers could be reached
还有就是在makedns时候,会在Getting reverse zones, this may take several minutes in scaling cluster. Updating DNS records, this may take several minutes in scaling cluster.停留很久。
最后cat /var/named/db.cluster.com
[root@mgmt3 ~]# cat /var/named/db.cluster.com $TTL 86400 @IN SOA mgmt3.cluster.com. root.mgmt3.cluster.com. (2013040901 10800 3600 604800 86400 ) IN NS mgmt3.cluster.com. mgmt3 A 192.168.10.254
之前一直遇到这个问题,发现这个问题已经在2.8中被修复了
http://sourceforge.net/p/xcat/bugs/3202/
当然如果也可以尝试用makedns -n来重新产生dns文件
然后在Scaling cluster那里很快就过了,并且db.cluster.com中也有信息了
[root@mgmt3 ~]# cat /var/named/db.cluster.com $ORIGIN . $TTL 86400 ; 1 day cluster.com IN SOA mgmt3.cluster.com. root.mgmt3.cluster.com. ( 2013040901 ; serial 10800 ; refresh (3 hours) 3600 ; retry (1 hour) 604800 ; expire (1 week) 86400 ; minimum (1 day) ) NS mgmt3.cluster.com. $ORIGIN cluster.com. ionode01 A 192.168.10.11 ionode02 A 192.168.10.12 mgmt3 A 192.168.10.254 node01 A 192.168.10.1 node02 A 192.168.10.2