Create an IIS website with a deliberate content path, application pool and network binding. This guide assumes the Web Server (IIS) role and the application's required runtime are installed on a supported self-managed Windows Server.
01 Prepare the site
Choose a unique site name, a dedicated application pool and a content directory such as D:\Sites\Example. Record the domain names, IP addresses and ports the site should use. Check existing IIS bindings so the new site does not compete with a working website.
Deploy the application from a trusted release and keep a backup of any directory you intend to replace. A folder used for customer uploads should have only the write access the application requires, separate from code that the worker process should only read.
02 Create and bind the website
- Open Internet Information Services (IIS) Manager. Expand the server and select Sites.
- Choose Add Website. Enter the site name and select the intended application pool, creating a separate pool when appropriate.
- Set Physical path to the deployed content directory. Verify that you selected the application root rather than a parent folder containing several sites.
- Configure the binding protocol, IP address, port and hostname. For name-based hosting, enter the exact hostname, such as
www.example.com, rather than leaving a catch-all binding unintentionally. - Review filesystem permissions for the pool and the site's configured authentication identity. Anonymous requests may use IUSR or the application-pool identity, depending on the authentication setting.
- Save and confirm the website and pool are started. Test a harmless page using the intended hostname through a controlled preview or correct DNS record.
- Add the required HTTPS binding and certificate before directing production customers to the site. Configure the Windows and provider firewalls for the intended public ports.
03 Verify the application
Test its default page, static files, login and any required write operation. If the wrong website loads, review DNS and binding selection before changing application code. If the request reaches the right site but fails, inspect the IIS status and application logs.
Common questions
Does creating an IIS binding create the DNS record?
No. The binding controls how IIS handles traffic that reaches the server. DNS must separately direct the hostname to the intended address.
Does selecting a runtime in the pool install that runtime?
No. Install the application's supported hosting components separately and verify their compatibility. The pool configuration cannot replace a missing application dependency.