<HTML>
<HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META content="OPENWEBMAIL" name=GENERATOR>
</HEAD>
<BODY bgColor=#ffffff>
<font size="2"><b>---------- Original Message
-----------</b>
<br />
From: Abdul Rashid Abdullah <webmaster@muntada.com>
<br />
To: BlueOnyx <blueonyx@blueonyx.it>
<br />
Sent: Thu, 10 Mar 2011 21:36:43 -0500
<br />
Subject: [BlueOnyx:06645] Multiple Sites to IP Address
<br />
<br />> As everyone knows, you can have multiple sites for an IP address when
SSL is
<br />>
not needed. However, there is a side effect. I had a customer who
put in
<br />>
mail.siteb.com and since there wasn't a web alias in the configuration, but
<br />>
another site, it resolved to <a target="_blank" href="http://www.sitea.com/">www.sitea.com</a>, because when it resolved the IP,
<br />>
that site was the IP address that was I guess the first site.
<br />>
<br />>
Of course, now he is upset because he has no affiliation with <a target="_blank" href="http://www.sitea.com/">www.sitea.com</a>.
<br />>
<br />>
In IIS, I can force host header resolution to the point where IP resolution
<br />>
won't work. In other words, <a target="_blank" href="http://www.sitea.com/">http://www.sitea.com</a> will work but not
<br />>
<a target="_blank" href="http://10.10.10.10/">http://10.10.10.10</a>.
<br />>
<br />>
How could we accomplish the same thing with BlueOnyx?
<br />>
<br />>
What I had to do in the mean time, was add all of the A records to the web
<br />>
aliases, but my thought is if he types in the IP address, he will get upset.
<br />>
Of course, I could just simply give him his own IP address and I might have
<br />>
to do that for this customer, but what about other customers?
<br />>
<br />>
Regards,
<br />>
<br />>
Rashid
<br />>
<br />>
_______________________________________________
<br />>
Blueonyx mailing list
<br />>
Blueonyx@blueonyx.it
<br />>
<a target="_blank" href="http://www.blueonyx.it/mailman/listinfo/blueonyx">http://www.blueonyx.it/mailman/listinfo/blueonyx</a>
<br /><b>------- End of Original Message
-------</b>
<br />
<br />
<br />My solution to that problem was to always use my support domain name as the first site of an IP address and then put a generic "Page Not Found" as the index page. Then, regardless of which other site with the same IP address was incorrectly accessed, it gave the generic "Page Not Found" message along with a message to contact myself as the hosting company. This solved the problem for us and the clients never ended up at the wrong site.
<br />
<br />Hope that helps,
<br />
<br />
<br />Dan Porter
<br />Twin Wolf Technology Group, LLC
<br />
</font>
</BODY>
</HTML>