Domain Name change help needed

[David Lockwood]

I have a network of HP Workstations and Servers which includes a ServiceGuard cluster. It has been decided by management that the Domain Name has got to be changed for the network. This has to be done because of the implementation of Active Directory. We hope to integrate LDAP with Active Directory so we can have common logins across PC's and Unix. Are there any prolems with doing this? Do I need to pay any particular attention to specific areas e.g. ServiceGuard? Do we need to consider anything special at the design stage of Active Directory? We will also (probably) change the NIS Domain Name. Any help and guidance would be appreciated.

[Steven E. Protter]

The domain name for active directory is linked to the DNS domain name. NIS need not be changed, though the term is the same its a different type of networking.

The change itself is simple, a change to /etc/resolv.conf as far as any search commands, followed by a quick check on /etc/rc.config.d/resolv.conf for anything that may need to be changed. Possible changes to /etc/hosts if you use that for name resolution.

Changing Domian resolution will affect openspool(no longer supported) and Data Protector Omniback if you use those products.

There are a number of products like oracle that may be effected by a change in domain name. The most important thing to do is to have a good test plan with backout options so if you get in too deep, or missed something you can back off and improve the process for the next run.

An Ignite backup of important servers prior to the change is a must.

Service Guard should be checked and tested thoroughly, though I can offer nothing specific in that area.

SEP

[Todd Whitcher]

Hi David,

If you use DNS/BIND in your environment and you want your Active Directory Servers and BIND servers to share data, SRV records etc, you should read this document by Cricket Liu the author of the BIND O'Reilly book.

http://www.linux-mag.com/2001-03/bind_01.html

For ServiceGuard you need to make sure that along w/ the hostname of the nodes the package name(s) are also updated w/ the new domain names. If your not changing IP addresses then you should not have any configuration changes that need to be made in the cluster binary or package configuration files. If your referencing the Fully Qualified domain names in any of your packages ( NFS Toolkit XFS options comes to mind ) then you will need to update those. The same goes for any clients that are accessing the SG cluster packages, if they are using FQDN just make sure you update their configurations to reference the new domain.

For NIS, if you are setting up a NIS/LDAP gateway a detailed decription of the setup process of the NIS/LDAP Gateway can be found
on http://docs.hp.com in the document "Installing and Administering NIS/LDAP Gateway". HP Part # J4269-90028

If your changing your NIS domainname there is a procedure outlined in the ITRC document ID A4982095. The Installing and administering NFS Services manual at docs.hp.com should also help you out HP Part # B1031-90048

If your using NFS, you will probably need to update your exports files on the servers and your automount maps or fstab entries on the clients.

Hope this helps, I'm sure our other Forum friends will offer some great suggestions.

Cheers,

Todd

[Bernhard Mueller]

Todd - excellent work deserves 10!

David,

one thing regarding NFS: typically people do not use FQDN for exporting and mounting NFS filesystems, HP-UX takes care of this. In this case, after a domain name change, you will have to restart rpc.mountd - just send it a SIGHUP;
else you will wonder why mount gives you a "permission denied" even after you re-exported everything.

Regards,
Bernhard