RPC over https - change of A record/reprecussions
Hi Team, I'm currently in the middle of swapping ISP (new stack of ip's). I'm currently running 2003 exchangesp1 on 2003 std., rpc over https with ssl on single server setup (small company 50 users tops)I'm going to have my ISP change the DNS A record for the domain name from the old static and have it point to the new static address. After propagation and all...I was wondering if this is all it takes? I'm wondering if I'll have SSL cert issues also, but at the same time they are assigned to dns names...so i'm thinking that will propagate over also (???)Has anyone had seamless success in this area? any advice? Feel free to critique.
September 30th, 2009 5:32pm

So long as only the IP is changing on the A record I don't think you'll have an SSL cert issue. One thing I'd recommend doing changing the TTL on the records to something much lower like an hour or less and allowing that change time to propogate, i.e., the old TTL expires. By doing this you'll be able to lessen the propagation time to almost instantly.Michael
Free Windows Admin Tool Kit Click here and download it now
September 30th, 2009 7:26pm

So long as only the IP is changing on the A record I don't think you'll have an SSL cert issue. One thing I'd recommend doing changing the TTL on the records to something much lower like an hour or less and allowing that change time to propogate, i.e., the old TTL expires. By doing this you'll be able to lessen the propagation time to almost instantly.Michael Thanks Michael...and yes the only one i'm changing is the A record...that's it. I'll remember the TTL info aswell. Thanks.
September 30th, 2009 9:29pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics