CName Host records

[Guest]

This is gotta be a simple thing. Notice how when you type in cnn.com it resolves and displays www.cnn.com in your browser? THis is what we need for our site since we have SSL enabled with a public certificate which is only associated with www.company.com. So when folks enter company.com and they try to access SSL protected pages they get a certificate pop up that talks about the the cert not being registered.

I tried adding a host record for www.company.com and then a cname record for company.com that points to www.company.com but when I type in company.com in my browser it doesn't resolve and then display www.company.com

What am I doing wrong? How do you do this?
Thanks

 

[Kevin D. Goodknecht [MVP]]

In

This is gotta be a simple thing. Notice how when you type in cnn.com
it resolves and displays www.cnn.com in your browser? THis is what we
need for our site since we have SSL enabled with a public certificate
which is only associated with www.company.com. So when folks enter
company.com and they try to access SSL protected pages they get a
certificate pop up that talks about the the cert not being
registered.

I tried adding a host record for www.company.com and then a cname
record for company.com that points to www.company.com but when I type
in company.com in my browser it doesn't resolve and then display
www.company.com

What am I doing wrong? How do you do this?
Thanks

Create a new website in IIS, with a host header for company.com then
redirect that site to https://www.company.com

 

[Jonathan de Boyne Pollard]

J> Notice how when you type in cnn.com it resolves and displays
J> www.cnn.com in your browser?

No, I don't. Because that's not what happens. DNS query resolution is
*not* what is doing this.

J> What am I doing wrong?

You are fiddling with DNS service when DNS service in fact _has nothing to do
with this whatever_.

J> How do you do this?

Consult your content HTTP server's documentation on how to publish
redirections with it.

Note, however, that redirections, either so-called "client-side" ones with
"<META>" or so-called "server-side" ones with 30x responses (both are in
fact enacted on the client side), are a poor way of going about things. For
best results, simply make the two web sites aliases of each other, and don't
employ redirection at all. Clients will then end up sending just one HTTP
request instead of two.

<URL:http://homepages.tesco.net./~J.deBoynePollard/FGA/web-allowing-omission-of-www.html#HTTP>