DNS Forward with parameters
I have a main domain (e.g. www.LongDomainName.com) and a short domain (e.g. www.shrtdm.com).
I have recently moved my corporate website into a fully hosted environment. Previously, we hosted the proprietary CMS. In my setup, I had IIS forward all requests for www.shrtdm.com to www.LongDomainName.com, including all parameters after the domain.
So IIS would redirect requests for http://www.shrtdm.com/contactus to http://www.LongDomainName.com/contactus. It was a wildcard redirect so it would work for any URL, not just predesignated ones.
Since we moved the system to the provider, we can no longer touch the backend. What I have currently done, is just point both domains "A" records to the same IP. This causes a problem with SSL certificate. Since, the short domain name gives users errors, since the certificate is for the long domain.
Can I redirect requests through the DNS system, rather then in IIS?
Thanks!
I have recently moved my corporate website into a fully hosted environment. Previously, we hosted the proprietary CMS. In my setup, I had IIS forward all requests for www.shrtdm.com to www.LongDomainName.com, including all parameters after the domain.
So IIS would redirect requests for http://www.shrtdm.com/contactus to http://www.LongDomainName.com/contactus. It was a wildcard redirect so it would work for any URL, not just predesignated ones.
Since we moved the system to the provider, we can no longer touch the backend. What I have currently done, is just point both domains "A" records to the same IP. This causes a problem with SSL certificate. Since, the short domain name gives users errors, since the certificate is for the long domain.
Can I redirect requests through the DNS system, rather then in IIS?
Thanks!
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
No, DNS is not capable of redirecting requests in this fashion. No matter what type of record you use, whether a CNAME or A, you can return the IP you want, but that won't help you with SSL since the URL will always be what was typed in (or clicked on) and so you get the name mismatch.
The two options I see are
- to change your SSL cert to use a UCC/SAN cert which you can specify multiple domains on, then pointing both A records to the same IP.
- set up a separate site for your shortname domain where you can do the same redirect as you were doing before.
The two options I see are
- to change your SSL cert to use a UCC/SAN cert which you can specify multiple domains on, then pointing both A records to the same IP.
- set up a separate site for your shortname domain where you can do the same redirect as you were doing before.
I'm not familiar with Netfirms.com (but I suspect any hosted solution would be the same) or PHP really, but I do know it's possible to create a page that will do a redirect instead of having the site configuration do it. In the past I've seen .aspx solutions, and I think a couple other types. I don't know how this would work if you wanted to redirect to different URLs (i.e. keeping the relative path after the domain). I'm sure you get a better response posting a question like that in the Topic area specific to what you're working with (e.g. PHP).
Premium Content
You need an Expert Office subscription to comment.Start Free Trial