Before reiping a machine, coordinate with 
<code>hostmaster</code> to set up the dns records.
Also, for <code>truststc.org</code>, you will need to
change the record at
<a href="http://members.ehost.com/webControl/domaindashboard/index.bml?tool=customdns">ehost</a>.

<p>After moving a machine and giving it a different name,
do the following
<ol>
<li>Change the name in /etc/hostname.hme0, /etc/nodename and /etc/auto_home.
 <li>Add the new hostname to /etc/hosts
<li>Change the name of the router in /etc/defaultrouter
<li>Change the name of the nameserver in /etc/resolv.conf
<li>Get ssh working for the www user so that we
can update php scripts
<li>Change the name in
/usr/local/apache/conf/httpd.conf and
php/include/conf.inc.php3

</ol>

After moving a machine and giving it a different ip address,
do the following
<ol>
<li>Edit <code>/etc/nsswitch.conf</code> and modify 
the <code>hosts</code> line so that the machine
will get its name from DNS:
<pre>
hosts:      dns files
</pre>
After the ip change, change this line back to
<pre>
hosts:      files dns
</pre>
<li>Change the ip address in <code>/etc/hostname.hme0</code> and <code>/etc/hosts</code>.
<li>Change the name of the router in <code>/etc/defaultrouter</code>.
<br>If your client is getting its address via dhcp,
then editing <code>/etc/defaultrouter</code> might
<b>not</b> be necessary.
<li>Change the name of the nameservers in <code>/etc/resolv.conf</code>
<br>See the <a href="http://idsg.eecs.berkeley.edu/network/#subnet-cory">IDSG Cory Networking page</a>
<li>If necessary, add the network to <code>/etc/networks</code>.
<li>After rebooting, verify that ssh works for the various users like
www.
<br>The old IP Address might be in the <code>~/.ssh/</code>
directory of some of the accounts to check.  
You may need to update these files:
 <menu>
 <li> <code>~bldmaster/.ssh/known_hosts2</code> on source
 <li>On andrews, check <code>/etc/init.d/chessnet</code>.
This file sets up the virtual interfaces.
 <li>Edit the firewall file: <code>/etc/ipf/ipf.conf</code>
on the machine that is changing and the dumphost.
 <li>Also, check in <code>/etc/inet/</code> for the 
old ip address.
 <li>The Virus Scanner needs to have the relay addresses
updated.  See <a href="http://www.gigascale.org/infrax/faq/155.html">What was done to install InterScan VirusWall on gigascale?</a>

Note that you can also edit <code>etc/iscan/intscan.ini
</code> and add relay ip addresses by hand, then 
restart sendmail:
<pre>
On Solaris:
    % <b>/etc/rc2.d/S88sendmail stop</b>
    % <b>/etc/rc2.d/S88sendmail start</b>
On Linux:
    % <b>/etc/init.d/sendmail stop</b>
    % <b>/etc/init.d/sendmail start</b>
</pre>
</menu>
<li>If you are changing the name of the website, then
update the DNS server for the the website, see
<a href="http://embedded.eecs.berkeley.edu/dopsysadmin/faq/114.html">Domain Name Servers</a>.

<li>If you are running mailman and the website name changes,
then you will need to modify the mailman setup or else
the web forms will not work.
The script <code>/home/www/php/mailman/updatemailmanwebsite</code>  does the following:
<br>For each mailinglist:
  <ol> 
  <li>Download the configuration:
  <pre>
/export/home/mailman_<i>N</i>/bin/config_list -o /tmp/mailman.txt <i>mailinglistName</i>
  </pre>
  <li>Edit <code>/tmp/mailman.txt</code> and change
  to the new website
  <li>Upload the new configuration:
  <pre>
/export/home/mailman_<i>N</i>/bin/config_list -i /tmp/mailman.txt <i>mailinglistName</i>
 </pre>
  </ol>

</ol>