HTTP/HTTPS

amyamandaallen

Hi,

Just dont know how this works - my rough example

I intend to registed our webserver on the net. I presume I find and pay someone who can register the server name and it obtains an internet DNS address. This will then give me access to our webmail on http://mywebmail.example.com. I then want a SSL certificate for it. I presume I can get this from somewhere like www.thawte.com. Do they then assign it a httpS/mywebmail.example.com address? Do the people who registered my webserver issue the https address? Do I istall the SSL certificate on my webmail server then reregister my address/dns entry?

Anyone who can help would be

ps - I hope my example makes sense!

sprkymrk

The owner of the server must do the lion's share of the work. Simply being the registered owner of a domain name is not enough. If you OWN the physical server that your webmail runs on, then you can contact one of the Trusted CA's to obtain a signed certificate. If it's a W2K or W2K3 server you can "sign it" yourself without paying a third party, but it will not be a trusted CA until everyone that accesses the server adds it to their trusted root store or trusted intermediate store.

amyamandaallen

I've just completed the THEORY with another pc but registered via no-ip.com. So I now see that the webserver can get a SSL cert from thawte but do I then need to get whoever registered the original mywebmail.example.com to a DNS address to change/add another DNS for [url]httpS://mywebmail.example.com[/url] or doesnt it matter if your putting http or https in front of it as long as the //mywebmail.example.com entry is registered.

Yes we do own the pysical box

JDMurray

Check out buying SSL certificates through your domain provider or ISP. They can be quite (in)expensive depending on your needs. Here's the SSL certs page at GoDaddy to get an idea of the variety of certificates: https://www.godaddy.com/gdshop/ssl/ssl.asp?se=%2B&ci=271

amyamandaallen

actually think I understand now

on the webmail box - I control if its coming in on http or https
I can block if the http one.

just need to get a registration for the server name.

correct?

sprkymrk

amyamandaallen wrote:

actually think I understand now

on the webmail box - I control if its coming in on http or https
I can block if the http one.

just need to get a registration for the server name.

correct?

You got it!

amyamandaallen

YAY

OK next part of the problem.

I know our domain is registered ok ( example - mydomain.com ) and we have a set off external registered IP address relating to each machine. Now one off the other webservers in our orginization can be directly accessed from the internet by typing http://otherwebservername.mydomain.com but I presume I also have to register the webmail servers FQDN with whoever we did the other working webserver, to get that visible on the net too?

thanks for help so far guys

sprkymrk

amyamandaallen wrote:

YAY

OK next part of the problem.

I know our domain is registered ok ( example - mydomain.com ) and we have a set off external registered IP address relating to each machine. Now one off the other webservers in our orginization can be directly accessed from the internet by typing http://otherwebservername.mydomain.com but I presume I also have to register the webmail servers FQDN with whoever we did the other working webserver, to get that visible on the net too?

thanks for help so far guys

Unless you want everyone to type the IP Address to access your webmail server, then yes, you need a DNS entry for it as well.

amyamandaallen

thats what I thought

thanks for clarifiying