Is there a way in 5.6 to force a DDNS update using the dNSName attribute of the AD server object?
In our environemnt, we manually set the dNSName attribute to example.org, while the ActiveDirectory domain is examplead.ad.example.org.
When the Celerra does a DDNS update for any server object, it registers the name of servername.examplead.example.org, even though the dNSName attribute of the server object was set to servername.example.org at creation/insertion time.
Yup, that's how we're inserting the server objects into the domain. From the command line, we use: server_cifs sample_vdm -Join compname=example.company.org,domain=prodad.ad.company.org,admin=admin-account-name
The dNSName attribute in this case does get set to example.company.org, but when Celerra does a DDNS update, it registers example.prodad.ad.company.org in DNS instead of example.company.org.