Sadly, not everyone has that option (I get to live in an environment where EVERYTHING gets a public IP. Joy.)
On 3/11/08 8:08 AM, "Don Ely" <[EMAIL PROTECTED]> wrote: > One would hope he had an FE server somewhere along the line... Not to > mention, one would hope he didn't have a publicly assigned address on his > Exchange box and was instead NATing the address on the firewall thus removing > any need to mess with the MX record... > > Hope, one would.. > > On Tue, Mar 11, 2008 at 8:00 AM, Joe Heaton <[EMAIL PROTECTED]> wrote: >> Don't forget your external MX record. >> >> Joe Heaton >> >> >> >> From: Joseph L. Casale [mailto:[EMAIL PROTECTED] >> Sent: Monday, March 10, 2008 8:37 PM >> To: NT System Admin Issues >> Subject: Changing ip of DC and Exchange server >> >> I have a W2k3 DC and Exchange server I need to reassign a new IP. Aside from >> DNS reflecting the actual data versus the old, what other things might I >> encounter? As long as DNS gets updated (which would even happen on its own >> over time) I can't think of anything else to worry about? >> >> >> >> Thanks, >> jlc >> >> >> >> >> >> >> > > --- > Salvador Manzo [ 620 W. 35th St - Los Angeles, CA 90089 e. [EMAIL > PROTECTED] ] > Auxiliary Services IT, Datacenter > University of Southern California > 818-612-5112 ~ Upgrade to Next Generation Antispam/Antivirus with Ninja! ~ ~ <http://www.sunbelt-software.com/SunbeltMessagingNinja.cfm> ~
