Changing server IPs...it didn''t work! :(

Re: Changing server IPs...it didn''t work! :(

From:

Date:

Time:

Andrew,

Let's see if I can summarize this problem properly:

- You set the Default TTL for the A record (not the MX record, not
the SOA record, not the zone's default TTL, etc.) to 1200 (20
minutes).

- You waited several days, far longer than the original TTL, so that
the old TTL would expire.

- You changed the A record to point to a new IP address, then waited
20 minutes for the rest of the world to notice.

- It didn't work. Mail continues to arrive at the old mail server.

Is that an accurate summary? If so, the only thing I can think of is
broken resolvers - some other DNS servers ignore TTL's. For example,
AOL is reputed to do this, caching records for weeks on end.

Is the problem still occurring? If so, your best bet is to leave a
mail server on the old server machine, such that it's set to relay
for all of your domains (relaying mail to your new server).
____________________________________________________________________
Chris Buxton Men & Mice
support@menandmice.com Making DNS Easy

At 6:30 PM -0500 12/28/01, andrew wrote:
>[i'm crossposting to both EIMS and QuickDNS lists in the hope that someone can
>explain this to me...sorry for the CP]
>
> > Is your old IP address still available? if so, add a secondary ip
> > addresses file to your preferences folder and server both addresses
> > until you are sure the old one isn't being accessed.
> >
>actually, I'm trying to "split" a server that was running both EIMS and
>QuickDNS.
>
>right now, the server in question is really the main NS for the domain...I
>originally had EIMS running on a different server but had to move it
>to the DNS
>server after 9/11.
>
>I've had it there ever since but want to move it back to it's original server.
>
>So I've got an A record in the DNS that points the MX record to the same IP as
>the DNS server right now.
>
>I want to reduce the caching of this A record so I can switch it
>back to the old
>IP...as I said earlier I set the TTL of the A record for the MX to 1200, and
>left it that way for about 5 days (the default TTL for the domain
>and SOA record
>are 86400).
>
>I then switched the A record for the MX to the new IP but the change was
>ignored, everything outside my subnet was continuing to point to the old IP
>address even an hour later.
>
>Would it help to globally change the TTL for the domain to 1200?
>
>TIA, Andrew
>
>
>----- Original Message -----
>From: "Jerry Jewell" <jj@tgd.com>
>To: "Multiple recipients of EIMS-L" <EIMS-L@qualcomm.co.nz>
>Sent: Friday, December 28, 2001 6:07 PM
>Subject: Re: Changing server IPs...it didn't work! :(
>
>
> > andrew wrote:
> > >
> > > Hi All:
> > >
> > > I posted earlier this week about changing the TTL on my MX
>record to 1200,
>in
> > > the hope that I could switch the IP address without
>interrupting everyone's
> > > access.
> > >
> > > The previous TTL had been 86400. I set it to 1200 about 5 days ago.
> > >
> > > I went ahead today and changed the IP for the mailserver, then
>set it back
>to
> > > 86400.
> > >
> > > I immediately received calls from people saying they couldn't
>connect to the
> > > server.
> > >
> > > When I tracerouted from a remote location to the MX servers
>name, it's still
> > > pointing at the old IP address....it's been almost an hour since the DNS
>record
> > > was changed and noone can connect except people using my DNS.
> > >
> > > Does anyone have a suggestion?
> > >
> > > TIA, Andrew
> > >
> >
> > Is your old IP address still available? if so, add a secondary ip
> > addresses file to your preferences folder and server both addresses
> > until you are sure the old one isn't being accessed.
> >
> > Jerry
> > WebDudes

Sales:
888/4-DPOINT

Support:
858/452-3696