Celerra DDNS and disparate dNSName

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.
Tags (2)
0 Kudos