IIS 7.0 and http??
masummiah said 1 year, 1 month ago:
I just bought a domain and configured the dns manager to point to my home IP since I am hosting it on IIS 7 using my Windows Server 2008; however, I am having some issue accessing my website.I can access https://MYDOMAIN.com and even the http://ftp.mydomain.com. I can’t seem to access my website using http:mydomain.com. For http access, I did the following bind.
type: http
Host Name: http://www.MYDOMAIN.com
port: 80
ip address: MY IP (ISP IP)
———————————————–
Type:http
host name: http://www.MYDOMAIN.com
port: 80
ip address: my LOCAL ip (192.168.0.102)
———————————————–
ALso, under SSL setting, unchecked under “requires SSL.” Any help is appreciated it and keep it novice level when explaining, I am a newbie. Thank you!
adamr said 1 year, 1 month ago:
@masummiah
It sounds like you may be working with a dynamic IP address. If this is the case, you will need to use a dynamic DNS service like dynDNS to point the domain to your server. You may want to check out this article I found at http://x.co/homeip.
Hope that helps!
-Adam
masummiah said 1 year, 1 month ago:
I am actually using namecheap.com free dns and I just pointed the NameServer to them and probably point the domain to my server from there. By the way, what is the record type for point the domain to my IIS 7.0 server?
adamr said 1 year, 1 month ago:
@masummiah
If you wish to manage the domain’s DNS through namecheap.com, you’ll want to point your domain to their nameservers using this article:
Setting Nameservers for Your Domain Names
If you would like to manage the domain’s DNS through your server, you’ll want to create custom nameservers that point to the static IP address(es) of your server using this article:
Registering Your Own Nameservers/Hosts
-Adam
masummiah said 1 year, 1 month ago:
Adam,
Is it easier to manage DNS through godaddy then using NameCheap since I’ve registered the domain here. All I want is to point my domain to my IIS web server, but this is getting way to complicated. I just can’t seem to load the web site using http://www.MYDOMAIN.com. Its funny how it loads HTTPS://www.MYDOMAIN.com, but its annoying due SSL certificate warning (self signed).
Also, If I change the default IP on the IIS binding from 80 to 8080 it works, however, I have to type in http://www.myDOMAIN.com:8080 which is a hassle.
masummiah said 1 year, 1 month ago:
I’ve contacted my ISP and said they block port 80, which was the source of my problems. I am using port 8080 now, but how can I just type in http://www.MYDOMAIN.com using port 80 instead of doing http://www.mydomain.com:8080 every single time?
P.S, I am thankful for your assistance!
adamr said 1 year ago:
@masummiah
You will be unable to specify a port for an A record; however, you can specify a port using our domain forwarding service. For example, you could forward the domain to:
123.45.678.90:8080
Forwarding or Masking Your Domain Name
Hope that helps!
-Adam
3 min expected wait time