Hi,
We are faced with having to change the DNS domain names on all of our
systems and we are still working out the impacts that these changes
will have on our day-to-day operations.
One of the areas that concerns us the most is the change's affect on
our backups. We are currently using DEC's NSR product to backup
about 20 systems, including an array of UNIX variants and a few
WinNT servers.
We are currently hoping that just adding the new FQDN of the client to
the list of hostname aliases in the client setup and adding the new
names of the servers to the list of authorized servers on the clients
will be sufficient.
I'm sure someone else has had to do this before, and we would like
to benefit from your experience in this matter. Are our plans
sufficient, or are we missing something?
Our servers are:
AlphaServer 8400, DU 3.2g, NSR 4.2a
TL812 Jukebox
Archive Server
Clients: DU, HP/UX, WinNT, Oracle (DMO2.0 run on remote system)
AlphaServer 2100, DU 4.0b, NSR 4.2b
2 TZ887 Jukeboxes
DMO2.0 Running locally
Clients: DU, HP/UX, IRIX, SunOS, WinNT, Oracle
Domain names:
Old: mdc.com
New: ???.???.boeing.com
The first two parts of the domain name haven't been formally
presented to us yet, but all of the rumored versions have four parts
to them in addition to the hostname.
We are also interested in hearing about any other gotcha's involved
with changing the DNS domain names on DU systems.
Thanks in advance,
Tom
--
+--------------------------------+------------------------------+
| Tom Webster | "Funny, I've never seen it |
| SysAdmin MDA-SSD ISS-IS-HB-S&O | do THAT before...." |
| webster_at_ssdpdc.mdc.com | - Any user support person |
+--------------------------------+------------------------------+
| Unless clearly stated otherwise, all opinions are my own. |
+---------------------------------------------------------------+
Received on Sun Aug 03 1997 - 02:37:22 NZST