Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have internal domain DNS for Http i.e. http://companyintanet.dev.local. Do I need a separate DNS entry for https i.e. https://companyintranet.dev.local or one will suffice both.

I'm trying to understand how DNS, Web Server Load Balancer and IIS works in terms of user reqest for http vs https.

Thanks.

share|improve this question

migrated from stackoverflow.com Feb 29 '12 at 15:20

This question came from our site for professional and enthusiast programmers.

    
To answer your question: No. DNS resolves a domain not a protocol. This is offtopic here btw. –  PeeHaa Feb 29 '12 at 10:10

1 Answer 1

No, you don't need a separate DNS entry for https.

You'll have an A record for companyintranet.dev.local. http or https doesn't come into play anywhere here. DNS doesn't care what protocol you're using to connect to a host, all it does is map a name to an IP address.

If you want to enable HTTPS on the server, you'll need to install a certificate and enable a site binding for port 443 (HTTPS) on the server, and tell it to use the certificate for that binding.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.