We’ve updated our Terms of Service. A new AI Addendum clarifies how Stack Overflow utilizes AI interactions.

Return to Answer

added 41 characters in body; deleted 1 characters in body

edited Apr 1, 2010 at 3:31

14k
19
73
102

I agree with Farseeker: stick to shared hosting and let someone else handle it.

However, if you must: I'm assuming you're planning on running Windows 2003 or 2008 on your VPS using IIS? If so, you can just create a new Web Site within IIS, and set the proper host header accordingly and you're good to go.

I'm assuming you're going to have a static IP with your VPS, so all you're going to need to do is create A host records in DNS* to point somedomain.com to your static IP: IIS' websites and host headers take care of determining what site to dish up based on the domain.tld that's requested.

Apache is the same thing with it's Virtual Hosts.

This, however, is not ideal: you'll want to isolate your clients (and client's code/files/data) from each other, which is likely already being accomplished through sheer necessity at your shared hosting facility (YMMV of course).

In the Linux/UNIX world, this isolation between users, processes, and system has been done for a long time using chroot/jails, not sure (besides full virtualization) how/if this is possible on a Windows Server.

*you can get an account at no-ip.com or zoneedit.com to allow you to manage your DNS records for your clients if their registrars don't provide the means to do so), but most do, like GoDaddy for instance.

I agree with Farseeker: stick to shared hosting and let someone else handle it.

However, if you must: I'm assuming you're planning on running Windows 2003 or 2008 on your VPS using IIS? If so, you can just create a new Web Site within IIS, and set the proper host header accordingly and you're good to go.

I'm assuming you're going to have a static IP with your VPS, so all you're going to need to do is create A host records in DNS* to point somedomain.com to your static IP: IIS' websites and host headers take care of determining what site to dish up based on the domain.tld that's requested.

Apache is the same thing with it's Virtual Hosts.

This, however, is not ideal: you'll want to isolate your clients (and client's code/files/data) from each other, which is likely already being accomplished through sheer necessity at your shared hosting facility (YMMV of course).

In the Linux/UNIX world, this isolation between users, processes, and system has been done for a long time using chroot/jails, not sure (besides full virtualization) how/if this is possible on a Windows Server.

*you can get an account at no-ip.com or zoneedit.com to allow you to manage your DNS records for your clients if their registrars don't provide the means to do so)

I agree with Farseeker: stick to shared hosting and let someone else handle it.

However, if you must: I'm assuming you're planning on running Windows 2003 or 2008 on your VPS using IIS? If so, you can just create a new Web Site within IIS, and set the proper host header accordingly and you're good to go.

I'm assuming you're going to have a static IP with your VPS, so all you're going to need to do is create A host records in DNS* to point somedomain.com to your static IP: IIS' websites and host headers take care of determining what site to dish up based on the domain.tld that's requested.

Apache is the same thing with it's Virtual Hosts.

This, however, is not ideal: you'll want to isolate your clients (and client's code/files/data) from each other, which is likely already being accomplished through sheer necessity at your shared hosting facility (YMMV of course).

In the Linux/UNIX world, this isolation between users, processes, and system has been done for a long time using chroot/jails, not sure (besides full virtualization) how/if this is possible on a Windows Server.

*you can get an account at no-ip.com or zoneedit.com to allow you to manage your DNS records for your clients if their registrars don't provide the means to do so, but most do, like GoDaddy for instance.

answered Apr 1, 2010 at 3:18

14k
19
73
102

I agree with Farseeker: stick to shared hosting and let someone else handle it.

However, if you must: I'm assuming you're planning on running Windows 2003 or 2008 on your VPS using IIS? If so, you can just create a new Web Site within IIS, and set the proper host header accordingly and you're good to go.

I'm assuming you're going to have a static IP with your VPS, so all you're going to need to do is create A host records in DNS* to point somedomain.com to your static IP: IIS' websites and host headers take care of determining what site to dish up based on the domain.tld that's requested.

Apache is the same thing with it's Virtual Hosts.

This, however, is not ideal: you'll want to isolate your clients (and client's code/files/data) from each other, which is likely already being accomplished through sheer necessity at your shared hosting facility (YMMV of course).

In the Linux/UNIX world, this isolation between users, processes, and system has been done for a long time using chroot/jails, not sure (besides full virtualization) how/if this is possible on a Windows Server.

*you can get an account at no-ip.com or zoneedit.com to allow you to manage your DNS records for your clients if their registrars don't provide the means to do so)