Scenario: an accelerator outside the firewall

About this scenario

In this scenario, the company wants to secure the data on the server (Web or streaming) from intruders. The company moved the server inside the firewall and deployed a NetCache appliance running as an accelerator outside the firewall. Because an intruder could not reach the server, the content would be secure. If an intruder broke into the accelerator, the intruder could not modify the data in any way.

Deployment illustrated

The following illustration shows a single accelerator.

To make this deployment work, the company could use either of the following methods:

Rename the Web server or streaming server and assign the accelerator the name that was previously assigned to the server. You can see in the previous illustration that the accelerator is named www.abc.com, which was the name of the server. As far as the users know, they are sending requests directly to the server because the URL they are entering is the same.
Define a local DNS name that NetCache can use to go to the IP address of the server that it is accelerating.
For example, www.abc.com would be advertised in the public DNS as the accelerator host name. The company would point NetCache to a DNS inside the local domain. The accelerator would have a virtual host entry for www.abc.com as the inbound host name and a matching destination of www.abc.com. The DNS that the accelerator points to would resolve www.abc.com as another address.