Hosting using IIS

[Title]

I have registered my domain with namecheap and want to host my website from home.

I have done all the port 80 (forwarding, firewall) steps I think.

I am using namecheap's Dynamic DNS Client.

I have the .html file in inetpub\wwwroot, and typing localhost in the browser shows my simple webpage.

My question is, how do I use IIS to allow people to type in my domain name and access my webpage?

 

[Thor86]

Couple of basic things:

1) If you are using a home router, which I suggest you do, and then port-forward TCP80 to your IIS webserver/system.

2) You need to setup your DNS (domain name) to point to the IP address of your internet connection. You can verify your current IP address by visiting - www.whatismyip.com.

 

[JackMDS]

You built a Web site using Authoring program ( like Expression Web).

You store the Pages on IIS (You have to find online help, or buy a book about IIS).

You make sure that your ISP does not block port 80; you open port 80 through the Router and Software Firewall.

The result would be that everyone in the world that types your domain name into the address box of their Browser would see your Web Site. Wow what a Magic.

However you really have to spend time on learning you will not get it right from Trial and Error and QA over forums.

http://technet2.microsoft.com/...9ddc1033.mspx?mfr=true

http://technet2.microsoft.com/...9ddc1033.mspx?mfr=true

 

[Title]

Alright, thanks for the pointers. My school gives Expression Web to us cs people so I will download that tonight, then read the links you gave me and hopefully I can figure out most of it from there.

 

[Title]

Alright, I have two specific questions.

What do I put in for host in the following?

pic

And does that affect what I put in this?
pic2
What IP address is it wanting under binding?


I've tried following the guides, but I feel these two things are holding me back.
I guess the main problem is I don't know how exactly I even use my registered domain (bought at namecheap).

 

[RebateMonger]

Most folks would create two Host Names ("A" Records) in your Public DNS records.

A dyingpc.com
A www.dyingpc.com

The Web Site Name in your second photo has no effect on publishing your web site. It's simply a convenient name to internally identify the site so you can modify its settings on your web server. The "binding" is telling what NIC and what TCP Port to listen for web site requests. "All Unassigned" and Port 80 should work fine for your purpose. I'm assuming you only have a single network card, anyway.

 

[mcmilljb]

Answer to Question 1:
For the host setting, you enter the host portion of the fully qualified name.
For example, www.microsoft.com is the full name, www is the host portion, and microsoft.com makes up the domain. So if you want people to type "vov.dyingpc.com" to reach your website, you leave it as "vov".
I looked at your dns provider, and they say they provide dns custom records. If your ISP provides you with a static ip, I would use that option rather than the dynamic ip address. It would say you from having to update the dns record each time your ip changes.

Answer to Question 2:
Physical path: put the location of your website files. If it is "inetpub\wwwroot", just click the "..." and browse to it.
IP address: put the IP address you want the server to listen to. I believe you can leave it unassigned and just use the Host header. When using HTTP 1.1, a web browser can send the URL along with the request so that the server knows which website it is intended for.
For example: If I want to go to www.microsoft.com. When the browser sends the request, it will include the URL "www.microsoft.com" in the actual request so the server knows I specifically want that website.

That should hopefully help. I am working on the Managing a Windows 2003 Server Infrastructure exam so this is the kind of stuff I have been working with.

 

[RebateMonger]

Host Headers are one way of identifying a particular web site when multiple sites are hosted on the same web server.

Each web site must have a UNIQUE combination of these three identification points:

1) TCP Port
2) IP Address
3) Host Header

For instance, you can host multiple web sites that use the same IP address and TCP Port, but each needs a unique Host Header. Changing the TCP Port is not usually very useful for public web sites because web browsers all use Port 80 by default. If you have only a single IP address and want to host on the standard Port 80, then you'll have to use Host Headers to identify the particular web site you want to access.