I have a client who hosts their main website with me, but part of the site ties in with their online transaction server at their office (an old IIS machine -- I hate that stupid machine <hehe>). They wanted it setup on a subdomain (secure.domain.com), so I got a static IP at their office, pointed the dns for the subdomain to that, and we were golden. Worked for years.
Recently, they got a fail over internet connection in their office. I wanted to make it so that if the office IP address changes (because their main line went down), people could still hit the secure.domain.com server. I recently set it up so that the CNAME "secure" went to the full domain name of their dynamic IP (something to the effect of domain.noip.org). I basically have their firewall at the office setup to update noip with their IP address, should it change.
While this works, is there any reason I *shouldn't* be doing this? I've seen anecdotal evidence all over that this is all fine and dandy, but I figured I'd ask here. SSL certificate on the IIS machine appears to still serve valid, I just want to make sure there's nothing I'm missing or I'm good to leave it like this.
Thanks!



LinkBack URL
About LinkBacks




Reply With Quote






