Complete Guide to Setting Up Subdomains on IIS 7: Key Technical Steps from DNS Configuration to Website Binding

Introduction

In web server management, subdomain configuration is a common yet error-prone technical task. Many developers configuring subdomains in IIS 7 environments frequently encounter situations where website bindings appear correct but remain inaccessible. Based on actual technical Q&A data, this article deeply analyzes the root causes of this issue and provides comprehensive solutions.

Core Principles of Subdomain Configuration

Subdomain configuration essentially involves two independent but必须协同工作的 systems: the Domain Name System (DNS) and the web server (IIS). DNS is responsible for resolving domain names to IP addresses, while IIS handles HTTP requests arriving at those IP addresses. When users enter SUBDOMAIN1.example.COM in their browsers, the first process that occurs is DNS querying.

The DNS system looks for the A record corresponding to SUBDOMAIN1.example.COM. If this record doesn't exist or is incorrectly configured, requests cannot reach the server. Even if requests do reach the server, IIS requires proper binding configuration to route requests to the appropriate website directory. Both环节 are essential and cannot be omitted.

Key Steps in DNS Configuration

Creating an A record for the subdomain in the DNS server is the primary step. Using a common DNS management interface as an example, the following record needs to be added:

Type: A Record
Name: SUBDOMAIN1
Value: 192.168.1.100 (server IP address)
TTL: 3600

This configuration tells the DNS system that when users访问 SUBDOMAIN1.example.COM, it should resolve to IP address 192.168.1.100. It's important to note that the subdomain's A record should point to the same server IP address as the main domain, unless there are specific architectural considerations.

IIS 7 Website Binding Configuration

After DNS configuration is complete, corresponding website bindings need to be created in IIS 7.以下是详细的配置步骤:

1. Open IIS Manager and navigate to the "Sites" node
2. Right-click on "Sites" and select "Add Website"
3. In the "Site name" field, enter: SUBDOMAIN1.example.COM
4. Set the "Physical path" to point to the subdomain's corresponding directory, for example: C:\inetpub\subdomain1
5. In the binding configuration:
   • Type: http
   • IP address: Select the server's IP address (same as the main domain)
   • Port: 80
   • Host name: SUBDOMAIN1.example.COM

Here's an example of relevant configuration that might appear in an ASP.NET Web.config file:

<system.webServer>
    <security>
        <requestFiltering>
            <requestLimits maxAllowedContentLength="52428800" />
        </requestFiltering>
    </security>
    <directoryBrowse enabled="false" />
</system.webServer>

Configuration Verification and Testing

After completing the configuration, systematic testing is required:

1. Use the nslookup SUBDOMAIN1.example.COM command to verify DNS resolution is correct
2. Check IIS binding configuration to ensure there are no port conflicts or duplicate host names
3. Access http://SUBDOMAIN1.example.COM in a browser for functional testing
4. Review IIS log files to confirm requests are being properly recorded

Common Issues and Solutions

During actual configuration, the following common issues may arise:

• DNS caching issues: DNS changes may take time to propagate; try clearing local DNS cache or waiting for TTL expiration
• IIS binding conflicts: Ensure no other websites are using the same host name binding
• Firewall configuration: Check if the server firewall allows inbound connections on port 80
• Permission issues: Ensure the IIS application pool identity has appropriate read permissions for the physical path

Advanced Configuration Considerations

For more complex scenarios, the following advanced configurations may need consideration:

• DNS configuration using wildcard subdomains (*.example.COM)
• Configuring URL rewrite rules in IIS to map subdomains to specific directories
• Configuring SSL certificates to support HTTPS subdomain access
• Using Application Request Routing (ARR) for load balancing configurations

Conclusion

Successfully configuring subdomains on IIS 7 requires proper协同工作 between two systems: DNS and IIS. DNS handles domain name resolution, while IIS manages request processing. Ignoring either环节 will lead to configuration failure. By following the steps provided in this article and understanding the role of each configuration item, developers can effectively manage and maintain multi-subdomain environments. Regularly checking DNS records and IIS binding configurations, along with implementing appropriate monitoring strategies, can ensure stable operation of subdomain services.