Asp. NET in the implementation of level two or multilevel domain name (modify urlrewrite) to pay attention to the problem __.net

1. Domain Name resolution problem
entered the domain name http://1234.abc.com/, browser prompts can not find the Web page. First of all, you should confirm that your domain name supports pan domain name resolution, that is, let all level two, level three domain names point to your server. Second, to ensure that your site is the default site on the server, that is, the 80-port host head empty site that can be directly with IP access to the http://1234.abc.com/, or to prompt your site error messages, or will be the correct implementation of your definition of urlrewrite, Either show the home page of your site.

2. Issues that cannot be overridden
If you confirm that your domain name resolution is correct, but still cannot rewrite, the access http://1234.abc.com/will prompt the path "/" Can not find ...,
If so, you first add the ASPNET_ISAPI wildcard application mappings (this step is required, sorry! not presented in the previous article).

How to: IIS Site Properties-> home Directory-> configuration




Click the Insert button



Select or enter C:/windows/microsoft.net/framework/v1.1.4322/aspnet_isapi.dll
Cancels the hook before the confirm file exists.
Are you sure

It should be no problem to visit the http://1234.abc.com/.


3. Default first page invalidation, because the ball to the asp.net processing directly, the default homepage of IIS definition will be invalidated, this situation occurs:
Access http://www.abc.com/cannot access the home page and can be accessed through http://1234.abc.com/default.aspx.
To solve this problem, please set lookfor/to/default.aspx or index.aspx in web.config. Rewrite, can completely solve the problem.