How to configure Server Topology for exposing an internal application for external access?

Question

Hi All,

I guess this question is bordering to a Server Fault question. I'd like to know the best configuration for exposing an internal application (in this case a load balanced Asp.Net MVC application) for external access.

More details about the situation:

1. The Asp.Net MVC Application is currently running on 2 servers
2. The 2 servers are behind a Windows Network Load Balancer
3. All the servers are on premise/internal network
4. I'm thinking of introducing an F5 Load balancer on off premise DMZ to replace the Windows Network Load Balancer. F5 will act as the public traffic gateway and load balancers to the 2 servers.
5. However, I'd like the internal users to not have go through the Internet to access the app.

The idea that I have so far is to keep both Windows Network Load Balancer and the F5. Each appliance will have its own IP and will have its own domain name. External users can use the public domain name which will hit F5, whereas internal users can use the internal domain name which will hit the Windows Network Load Balancer.

Is this a good idea? Or is there a better way of doing this?