Reply to Message

Reply to Message

View discussion in a popup

Replying to:

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, while the ActiveDirectory domain is

When the Celerra does a DDNS update for any server object, it registers the name of, even though the dNSName attribute of the server object was set to at creation/insertion time.
Tags (2)
0 Kudos