Reported by Arif on xcat mailinglist.
"The issue that I have now at a customer site is that the networks.nameservers is populated as the MN,SN1,SN2, i.e. the Management node and the 2 service nodes. For this specific scenario, the hosts within the network is being ignored, i.e.
Ignoring host node001, it does not belong to any nets defined in networks table or the net it belongs to is configured to use an external nameserver.
"
The reason is from the code in ddns.pm:
unless (($->{nameservers} eq $myip) || ($->{nameservers} eq '<xcatmaster>') || ($_->{nameservers} eq $sitens)) </xcatmaster>
so in this check, if the networks.nameservers is not mn's IP facing networks.net, or <xcatmaster>, or site.nameservers, then we exclude this net from dns zones.</xcatmaster>
We need to consider the multiple nameservers case in the code, the fix is to split the networks.nameservers first instead of using it directly.
The fix has been checked into both 2.9 and 2.8.3.
commit fb60b65258d42a04dec6c822ce4c99d52a37b33e
Author: sjing sjing@cn.ibm.com
Date: Thu Oct 24 04:19:47 2013 -0400