Does anybody know if ordering/installing nameservers will solve the following problem?

I get an error after instalation of SSL certificate on a W2K and Resin servers. When I redirect a domain www.mydomain.com to secure https://111.222.333.444/folder (using directNIC service), it says
that the domain www.mydomain.com does not match with what is put in the security certificate. However, I have the same www.mydomain.com put in the security certificate. I think the problem is that redirection goes to IP without any domain name information passed.

Can it be a problem with server configuration?

Your browser looks at the URL it's actually at and compares it to the certificate. If you're visiting https://11.22.33.44/ that won't work unless the certificate is issued to 11.22.33.44. The URL has to match the certificate exactly.

If you're using some kind of domain forwarding service, you will have to change it to return a real DNS answer so that www.domain.com resolves to the IP address you're using (and yes, this means a dedicated IP for the site; you can't do shared IP hosting with SSL).

Kevin

Yes, I use domain forwarding service and it forwards to a static IP. I do not have my own nameservers.

How do I change it to return a real DNS answer (and what does it mean)? I was also wondering if outsourcing a namerserver would solve the problem?

Originally posted by broadwayspot
Yes, I use domain forwarding service and it forwards to a static IP. I do not have my own nameservers.

How do I change it to return a real DNS answer (and what does it mean)? I was also wondering if outsourcing a namerserver would solve the problem?

The nameservers for your domain need to return an IP address that is uniquely assigned to your site, and the Web server answering at that IP address must serve your site via SSL. What you have right now is the domain forwarding service returning its own IP address for the site, and then when someone visits that IP address, issuing a redirect to the http://11.22.33.44/ you mentioned.

Explain what you're trying to achieve to your domain forwarding service and see if they have a solution; if not, find a new service. Surely the host running the SSL can help you out?

Kevin

I think I'll need new domain forwading service. Can you recommend a good one?

And I host the site on my own server.

You might check out www.zoneedit.com or www.afraid.org

Have you tried URL cloaking? May be that can help.

hmm maybe you've registered the SSL certificate with the domain-name: domain-name.com --> and not with www.domain-name.com or *.domain-name.com Try to go to https://domain-name.com instead of https://www.domain-name.com maybe that's the problem.