I believe the easiest way to obtain your desired results is to change the way you created the new site. If you create the new site with a host header and on port 80, then you wouldn't have this issue. The cname in DNS just points users to the server, not the particular IIS site. IIS has to be listening...