|
Posted by Jim Watt on May 11, 2007, 1:48 pm
If you were Registered and logged in, you could reply and use other advanced thread options
On 11 May 2007 08:03:04 -0700, girardmj375@yahoo.com wrote:
>We are in the planning stages of relocating our office, and we had
>some concerns about forwarding our web site and the effect it would
>have on our secure site.
>
>We currently have our secure site established as https://www.company.com/access
>and everything works fine because the certificate is registered to
>company.com. However, after we relocate, we will be forwarding
>requests for this site from our old office to the webserver in the new
>office during the time it takes the DNS records to populate the web.
>We were planning on using the IP address of the webserver in the new
>office to accomplish this.
>
>When we test this out at our current location, and try to access the
>the site using the redirect address of https://203.XXX.XXX.XXX/access,
>we get an SSL error stating that "The name on the security certificate
>is invalid or does not match the name of the site", which is expected
>because we are now using the IP to access the site rather than the
>domain name that has been registered.
>
>Does anyone know of any way to get around this so that our clients
>don't recieve this error in the day(s) it takes for the DNS record to
>populate. I realize it will only be for a day or two for the records
>to populate and users can simply click "Yes" to get past the warning,
>but we would rather figure out a way around this to avoid getting the
>calls that are sure to come when clients see the warning message.
>
>Any help is greatly appreciated.
A few days before you do the move change the TTL on the
DNS records to the minimum value.
Relocate the web server as 'company.com' and then increase
the TTL to a normal value.
--
Jim Watt
http://www.gibnet.com
| 
XML site map