How to modify CIFS server FQDN ?

Did you join the CIFS server from the command line or the GUI?  From the command line, you can use the FQDN of the host in DNS and use your expected AD realm.  Something to the tune of:

server_cifs server_2 -add compname=myserver.dnsdomainname, domain=MYDOMAIN, interface=my_interface

Then, join the CIFS server to AD with:

server_cifs server_2 -Joincompname=myserver.dnsdomainname, domain=MYDOMAIN, admin=

The document "Configuring and Managing CIFS on VNX" has more specifics on the command line options and caveats.

Let us know if that helps!

Karl

Thanks Karl

I was hoping there would be another way (without service interruption) 

I will do that : Unjoin, delete, then add and join with FQDN name.

Nicolas

The nice thing is - with the command line, you can script the unjoin, delete and add - or at the very least, add them in a series of commands, separated by semicolons.  Then, the commands execute one after another. You can then execute the Join command and get the right DNS name in place.

I would highly recommend downloading the VNX simulator and trying this out.  With practice, you can probably get the entire process to take less than two minutes!

Let us know if that helps!

Karl

i would be careful with delete especially if you use local groups/users.

Can't you just add a search suffix to the Celerra so the short name would resolve correctly,  and avoid the downtime? I know it's nice what would be idea,  but should get you by..

The data mover is already configured with the correct search suffix. I don't think that modifying the search suffix can help : according to nas_checkup report, the DNS resolution test seems to be made against the FQDN (not the short name)

By the way, even after the 4 steps procedure (unjoin/delete/add/join) with the correct FQDN name, I still have the problem :

The nas_checkup is still complaining about missing DNS records.

The server FQDN is still FQDN=myserver.mydomain when invoking server_cifs command

But :

The DNS properties of the computer object in AD is now the correct FQDN myserver.dnsdomainnam

Local groups definitions were kept even after computer deletion. Maybe the same applies for FQDN. Do you think that there are some "cached" information that should be purged prior to computer add/join operation.

Nicolas

You may be set to manual DNS update mode... Run this to verify:

server_param server_2 -facility dns -info updateMode -verbose

Check out the current value... It needs to be "2" to allow for dynamic updating... "1" might work as well,  for an unsecured update... but that isn't recommended... "0" is setting it not to update...

Also when joining the domain are you specifying a user which has access to create the computer, etc?  I noticed your server_cifs command was lacking the usual "admin=" bit...

Can you show us the output of "server_cifs server_2"  (or whatever datamover we're talking about here...)

Enabling Dynamic DNS on the Celerra will cause it to notice any manual changes you've made to the DNS records - it gets you out of having to unjoin/join the domain like you did...

I have noticed that even if i create a new computer with the correct DNS FQDN

server_cifs server_2 -add compname=myserver.dnsdomainname, domain=MYDOMAIN,

FQDN is never correctly reported when running server_cifs command

server_cifs server_2

CIFS Server MYSERVER[DOMAIN]

Full computer name=myserver.mydomain realm=MYDOMAIN

  FQDN=myserver.mydomain (it should be myserver.dnsdomainname)

And nas_checkup keeps complaining about unresolved DNS records.

I will call support.

Thanks for your help

Nicolas

Hi Mark,

Indeed I am not using dynamic updates, I wish I could .

Our DNS server does not support dynamic update.

Thanks anyway

Nicolas

Right,  often in server_cifs output will return some information in parentheses after the FQDN.  In your output you have your comments in that section.  Does the output have anything in that space?

Yes, I use a specific user when joining the computer to the domain (admin=....) but the computer account is already created in the AD before the join (delegated join)

the server_cifs command returns

CIFS Server MYSERVER[DOMAIN]

Full computer name=myserver.mydomain realm=MYDOMAIN

  FQDN=myserver.mydomain (it should be myserver.dnsdomainname)

Let us know what the root cause was