That sounds like you're doing something similar to Apache's Name Based
Virtual Hosting on the IIS Server. I've never run IIS, so I have no
idea. But this is not a Network level issue, it's a web server issue.
Apache would have something like this:
<VirtualHost 1.2.3.4>
ServerName zeus.xxxxxxxxxx.com
DocumentRoot /www/zeus/html
<Directory /www/zeus/html>
Order deny,allow
Allow from all
</Directory>
</VirtualHost>
<VirtualHost 1.2.3.4>
ServerName intranet.xxxxxxxxx.com
DocumentRoot /www/intranet/html
<Directory /www/intranet/html>
Order deny,allow
Deny from all
Allow from 1.2.3.0/24 # OUR LOCAL SUBNET
</Directory>
</VirtualHost>
So not a Layer 3 or 4 decision here. This is a Layer 7 issue.
Bruno Nunes wrote:
Hi,
I have:
intranet.xxxxxxxxxxx.com -> ip A
zeus.xxxxxxxxxxx.com. -> ip A
both are redirections made with iptables to make ip A (local) accessed
by world wide. When someone tries to access zeus or intranet by the
hostname the host machine running IIS knows which website the user is
trying to access.
my problem is:
how to block intranet.xxxxxxxx.com to be accessed by worldwide if it
has the same ip as zeus.xxxxxxx.com? can i block by hostnames instead
of an ip address??
thanks
--
Brad Lhotsky <lhotskyb@xxxxxxxxxxxxxxx>
NCTS Computer Specialist
Phone: 410.558.8006
