ISP changing IP's on me and I was wondering the proper precautions for moving to a new IP

[ksscendyn]

Its been a while fellow toasters...

My Toaster is currently 3.1.1 (never have needed to upgrade)

Anyhow I need to know what exactly I need to change for the transition to go smoothley for a new block of IP's... since I dont have but 1 server ATM.  Yes I am building a new server this month : )

I figured I would have to change these things
in no particular order without rebooting.

1. Apache Virtual Hosts and SSL including my certs
(apachectl stop and restart ssl I can do it)
2. DJBDNS since I run everything off a block of 5 ip's
(just run a make in the directory and update it once edited)
3. hosts
(not sure how to resig this)
4. rc.conf
(not sure how to resig this either)
5. TCP Server <--- not sure how to do this without killing it
(this one I am scared of hehehe)
6. and anything else I forgot which I am sure there is...

Basically if anyone can give me the answers so to speak and which files I did not put up that need editing .. and how to go about all this without REBOOTING is the key I am not a pro with UNIX commands but been running a toaster thanks TO MATT S. for 2 years strong with no hicups was up and running for 264 days zero downtime. Then it rebooted ... doh.

[matt]

The best thing to do is add the new IP to the system. If you're using a "stock" Mail::Toaster, then all the services automatically bind to all active IPs. So, I'd do something like:

Example:
 old IP:  192.168.0.1 mask 255.255.255.0
 new IP:  10.0.1.1    mask 255.255.255.0

1. Add new IP to /etc/rc.conf (in case the system reboots).

   ifconfig_fxp0_alias0="inet 10.0.1.1 netmask 255.255.255.0"

2. Add the new IP to the interface, such as:

   ifconfig fxp0 10.0.1.1 netmask 255.255.255.0 alias

3. When your ISP has your new IPs active, test everything on the new addresses and then update your DNS as appropriate.

4. You'll have to update the (few) places where your IP is embedded, such as the djbdns env/IP files.