Forum Moderators: open
I would like some advice with regards to hosting a variety of websites and corresponding domain names on our own servers.
We currently have a single IIS webserver, which we plan to build on in the future, but for the moment i have created and uploaded our website on this machine. My main problem is the domain name and getting it to point to the correct webspace. I dont see this as being a problem for the default website as a simple redirect from a nameserver would probably suffice, however we have a number of clients requiring us to host their websites in the near future and I dont know how this is possible other than setting up a name server of our own. (I think!)?
As you can guess I am new to the business of web hosting so any input would be greatly appreciated.
Thanks
I think there are some problems with IIS and host headers though - with SSL particularly. Look in the MSKB.
Better solution would be to obtain multiple IP addresses, and multi-home your computer to listen on all of them. Under TCP/IP Properties, click the advanced button (in network connections), and add all the IP addresses that you will be using.
Each website will listen on a particular IP address, which you can configure under Computer Management->Website Properties -> IP Address. This will list all the IP Addresses available on your server.
HTH-
WDSF
I tried answering your post earlier but this happened [webmasterworld.com]. Anyway, I'll try again :-)
First of all, to run multiple websites from IIS you need to be running a server edition of the OS i.e win2k server or advanced server. The professional edition doesn't let you run more than one site.
To run more than one site on IIS you right click on the name of your server in the IIS management console and select new -> web site. During the wizard you will be asked for a host header, this should be the full domain name of the site i.e www.example.com.
You may find it easier to use your ISPs DNS servers rather than install your own. Most ISPs allow you to modify the DNS entries for domains purchased through them. You would need to add a new 'A' record for www.example.com that points to your IP address. IIS would then route a request for that name to the right site using the host header information.
Hosting is a two stage process. A DNS record must be setup which directs a request to the correct IP address. It is then the job of the web server to direct the request to the correct site.
If you do want to host your own DNS these posts may help.
[webmasterworld.com...]
[webmasterworld.com...]
[webmasterworld.com...]
Webdevsf makes an interesting point about IIS host header issues although, in practice I have never experienced any problems with this. Also, IP address' cost money and because of these reasons, personally, I wouldn't second his opinion that separate IPs are a better option.
Good luck!
Cheers
Stretch
So any particular port (typically 443 for SSL) and IP address must go to a unique SSL site.
I have a remote located host which I control viy remote desktop. It has around 8 IP addresses and dozends of websites, and I jsut love the freedom and flexibility apahce gives me. I also run apache on my development machine with a few dozend domains (sub domains on dynamic DNSes) And everything works so beautifully. First on a plain win98 and now on winXP pro, no need fo rany server OS.
consider apache, it'll make your life so much easier and your setup so much more transparent. IIS always frustrates me by the simple fact that often you can'T figure out how to do something, where to do it or if IIS can even do it at all.
SN
IMO, you have to hang with IIS for a while to get the hang of it. I find that [localhost...] is the place to turn when you have a question. You can use a little VBScript to modify the metabase - this comes in handy when you have to manipulate a lot of things at one (like, set the expiration header on every .asp page on the site, while leaving the .jpgs alone.)
Chris
