I originally had a server hosting SiteA on all unassigned IP (it is also SSL on 443 but that's besides the point). Then I had a need to host a second site, with both SSL and two host headers to this same new site, on this machine. Knowing that the SSL on one IP would be a problem, I added a second address x.x.x.89 to this server. I set the original SiteA to bind explicitly to the original IP x.x.x.38 and then set the new site with the two new host headers SiteB and SiteC to explicitly bind to x.x.x.89 for both host headers. I added A records to DNS for both SiteB and SiteC to point to x.x.x.89.
On the local LAN (browse from my PC), SiteA continues to be served just fine, no problems. SiteB is served fine. SiteC is served fine.
From the internet, SiteA serves fine. SiteB and SiteC show 404 errors, and when I investigate the httperr.log, it shows these requests going to SiteA at x.x.x.38:
2013-04-16 17:27:43 166.78.x.x 49298 x.x.x.38 80 HTTP/1.1 GET / 404 - NotFound -
2013-04-16 17:27:49 166.78.x.x 49299 x.x.x.38 80 HTTP/1.1 GET /bad.htm 404 - NotFound -
What am I doing wrong here? I am also seeing some requests in httperr for SiteA that got sent to x.x.x.89, and these are coming from DHCP clients on the LAN:
2013-04-16 17:19:20 172.20.y.y 60319 x.x.x.89 80 HTTP/1.1 GET /Shared+Documents/Forms/Active.aspx 404 - NotFound -
2013-04-16 17:24:03 172.20.y.z 62637 x.x.x.89 80 HTTP/1.1 HEAD /Shared+Documents/Clients/OneNote/files/ 404 - NotFound -