Our business has a split DNS environment (hosts belonging to mybusiness.com in both Intranet and the Internet). We are using ISA Server 2004, but our workstations do not have the Firewall client installed. Their web browsers (IE 6) have the ISA machine set up manually as the proxy server. Workstations' default gateway is NOT the ISA machine.
I'm cooking my noodles to figure out a way to implement access to all of our websites because of the split DNS scenario. Basically, the majority of our web servers are in the Intranet, EXCEPT for two of them (I will call them abc.mybusiness.com and xyz.mybusiness.com for clarity's sake).
So at this point, we are accessing our sites using the most "dumb" manner, which would be including *.mybusiness.com in the browser's exception list, and removing that when we need to access abc.mybusiness.com and/or xyz.mybusiness.com.
As one can imagine, that is quite cumbersome (very happy users!). I did some research and found out that a .pac file can do the trick for me, because unlike the browser (IE), it works with a exclusion list and also a inclusion list, letting me force specific sites to go thru the proxy.
But my question is: can't I do such a configuration inside ISA Server? I'd rather just have the workstations' web browsers point to my ISA machine and let ISA do all the heavy-lifting... Not having to deal with a .pac file would be only less thing to worry about, configuration-wise. But so far to my understading, ISA's Direct Access list would work the same way as the browser's exception list (the difference being centralized configuration)