Avoiding redirect loop

[virgvv]

I know the basic rules of 301 rewrite and redirection, but I've got a situation with a client site that I'm not sure how to handle.

His current site (an ecommerce store) is www.domain-A.com. He has a 2nd domain name, www.domain-B.com, which forwards to Domain A.

We're moving the store to a new server, and he also wants to use Domain B exclusively from now on.

I've set up redirects in the old Domain A ASP files (new store is a LAMP setup), but until Domain B propagates at the new address, I think we'll get a loop that's going to throw 500 server errors. Domain B redirects to Domain A, which redirects to Domain B...

One way to handle the problem is to set up Domain B at the new address and leave the old store up at Domain A for a day or two, until I'm sure Domain B has propagated.

But is there a more elegant way to do this?

Thanks.

[coopster]

Assuming you have access/control of the zone files you can crank down the TTL on the domains to a low TTL, five minutes or even five seconds if you want. Once you are certain the new TTL has propagated you can put the new redirection in place. And once you are happy with everything you can flip the TTL back to normal.

[virgvv]

Thanks! Didn't even think of that.