Change of DNS name

Valerio wrote:

> Jason Bolinger wrote:

> > William Arijs wrote:

> > > The server on which we have Tarantella running will be moved into a

> > > different network. So, this means the domain on the Unix box will have

to

> > > be changed, also the DNS name will be changed.

> > > What needs to be done in order to update our Tarantella configuration for

> > > the new situation?

> > > We are running Tarantella 3.2 on Solaris 2.6.

> > > Thanks,

> > > William

> > The following is something I have recieved from Tarantella about a year

> > ago to solve the issue you are looking at.

> > Hostname changes - attached is "recipe" for changing the DNS name of a

> > server which we have tested. Note that changing the DNS name if the unit

> > is still in evaluation mode causes it to fail.

> > HOW TO RECONFIGURE TARANTELLA AFTER DNS NAME CHANGE

> > ==============================================================

> > In general Tarantella server DNS name change is a four step process:

> > 1. Stop Tarantella server

> > 2. change DNS on Unix/Linux Server (/etc/hosts, /etc/resolve.cnf, change

> > DNS tables of name server etc).

> > 3. reconfigure tarantella (see example below)

> > 4. restart Tarantella

> > There are a number of caveats that should be noted:

> > a. TSP certificates may be invalide (certificate are tied to host name)

> > b. IP filtering may be referring to wrong server namne

> > c. ens database will have objects referring to old server name

> > d. if for some reason dns changes require your system to be rebooted make

> > sure that your S90Tarantella in rc is moved.

> > e. when the host is part of an array the host needs to be isolated from

> > the array first.

> > Example =======

> > Old host name = ripple.tarantella.com (152.126.28.38)

> > New host name = maverick.taranella.com (152.126.28.34)

> > 1) Stopped Tarantella

> > 2) Edited the following files, replacing all "ripple" references by

> > "maverick":

> >var/info/master

> >var/info/ports.properties

> >var/serverconfig/global/ripple.tarantella.com.properties

> >var/serverconfig/local/bootstrap.properties

> > 3) Renamed var/serverconfig/global/ripple.tarantella.com.propertiesas

> > var/serverconfig/global/maverick.tarantella.com.properties

> > 4) Change system name and IP address.

> > 5) Verified that ttahostname returns the correct FQ host name.

> > 6) Ran "tarantella setup", and told it to recreate default webtop objects

> > and Tarantella printer.

> > 7) Ran "tarantella start".

> > Tarantella should now be up and running, the only obvious problem being

> > that the default objects all exist in pairs (one each for the old host

> > name and the new host name). The old ones can either be deleted manually

> > (by OM or command-line tools), or it should be fairly easy to write a

> > script to do it.

> > This procedure fixes only the default webtop objects. If any other

> > objects have been created to run on the old host name, there is currently

> > no way to reassign them automatically. I don't think there should be any

> > problem with true tier 3 apps (as opposed to apps which run on tier 2,

> > masquerading as a tier 3).

> > Passwords cached under the old host name will be inaccessible, and will

> > have to be re-entered.

> > The scenario described above was a standalone server. It's highly likely

> > that other things would need to be changed if the server was in an array.

> > Hope this helps.

> I was going crazy with version 3.4: I only changed the IP addresses (non

> the dns name) and tta was generating all the print file correctly before

> the tta print_converter and 1 byte sized after...

> The only thing I do, afeter verifying all the file you suggest, is

> "tarantella setup" (only with printer recreation option) and it seems now

> it's ok.

> Thank you very much!

> Ciao

> valerio

Guest at 2007-7-4 18:50:48 >