I have no idea what is going wrong with the setting, the DSFW installation completed without problem but it failed at the Configure DNS during Provisioning Wizard. The DSFW Server listed as the 1st nameserver in the /etc/resolv.conf, it should be all right.

Below is the part of provisioning log...

2010-01-21 13:17:53 proceeding with the next entry
2010-01-21 13:17:53 /opt/novell/xad/lib/perl/NDS/import.pm:103 Could not process the entry
2010-01-21 13:17:53 /opt/novell/xad/lib/perl/NDS/import.pm:104 dn: cn=DNS_domainSFW,ou=OESSystemObjects,o=st
changetype: modify
add: dNIPZoneList
dNIPZoneList: cn=st_gov_my,ou=OESSystemObjects,o=st
2010-01-21 13:17:53 /opt/novell/xad/lib/perl/NDS/import.pm:105 LDAP_TYPE_OR_VALUE_EXISTS:The request attempted to add an attribute type or value that already exists

2010-01-21 13:17:53 proceeding with the next entry
2010-01-21 13:17:53 /opt/novell/xad/lib/perl/NDS/import.pm:103 Could not process the entry
2010-01-21 13:17:53 /opt/novell/xad/lib/perl/NDS/import.pm:104 dn: cn=DNS-DHCP,ou=OESSystemObjects,o=st
changetype: modify
add: dNIPDNSZones
dNIPDNSZones: cn=164_22_1_10_in-addr_arpa,ou=OESSystemObjects,o=st
2010-01-21 13:17:53 /opt/novell/xad/lib/perl/NDS/import.pm:105 LDAP_CONSTRAINT_VIOLATION:The request contains a value which does not meet with certain constraints.
This result can be returned as a consequence of

* The request was to add or modify a user password, and the password fails to
meet the criteria the server is configured to check. This could be that the
password is too short, or a recognizable word (e.g. it matches one of the
attributes in the users entry) or it matches a previous password used by
the same user.

* The request is a bind request to a user account that has been locked