Date: Wed, 5 Mar 2003 20:35:47 -0800 From: clark shishido <clark@ruminary.org> To: tony <tony@saign.com> Cc: "freebsd-isp@freebsd.org" <freebsd-isp@freebsd.org> Subject: Re: IP addresses changing... Message-ID: <20030306043547.GA39370@ruminary.org> In-Reply-To: <200303060331.h263VajI021210@p3.saignon.net> References: <200303060331.h263VajI021210@p3.saignon.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Mar 05, 2003 at 07:31:36PM -0800, tony wrote: > > I have 5 days.... > lower the TTL on all your DNS records now. do you have to change your authoritative name servers? if yes, ask your ISP if you can set up new name servers beforehand. assign an alias and static routes to all your existing servers for the new network. Keep your existing configs and add on changes for the new IPs. If you're in more than one broadcast domain, convert one of your boxes into a router or create one. The strategy is to keep things running as they are, and cut over to new IPs afterwards. It's easier to add access than try and figure out why something is not working (hard-coded IP access lists). After the ISP's cutover is complete then start removing the old IPs and rebooting boxes so things come up cleanly in the new config (new IP and old IP aliased). If you have a lot of hard-coded networks, keep aliases and/or staticly route the old network so all your machines can still find each other. Final steps, remove aliases and static routes. This way critical services like http & smtp will migrate immediately, and you can get to graphing/monitoring/security later. --clark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030306043547.GA39370>