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
4 Replies
Highlighted
8 Krypton

Re: Celerra DDNS and disparate dNSName

are you sure the dNSName attribute is still set to servername.example.org ?
I think we change that when we join the CIFS server to the domain.

you can try creating a test CIFS server using the disjointed namespace way (see CIFS manual page 114) if that makes a difference ?

like this:

server_cifs server_2 -Join compname=cifstest.example.org,
domain=examplead.example.org,admin=administrator@examplead.example.org
0 Kudos

Re: Celerra DDNS and disparate dNSName

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.
0 Kudos
8 Krypton

Re: Celerra DDNS and disparate dNSName

could you please open a service request for that so the support can check whether its a bug or not ?
0 Kudos
8 Krypton

Re: Celerra DDNS and disparate dNSName

how about the dns= option of server_cifs ?
0 Kudos