Scenario: Dev team wants to resolve test-www.secondsite.com to an internal IP for testing purposes.
Option#1: put internal IP address of the server on the external DNS zone, (don’t like having internal IPs on an external zone, but it would work)
Option#2: Setup a reverse proxy on the external zone and send the test users through the firewall (don’t like having the test sites available to the outside world)
Option#3: Use an internal zone we have already setup to test sites for other zones we don’t want to make internal zones for (test-secondsite-www.mainsite.com pointing to the internal server of www.secondsite.com’s test server. Will have to add bindings to the IIS server to accept this new header)
Option#4: Create an internal zone for the secondsite. I really dislike this option, because it has to be constantly managed and any record changes on external would have to be replicated internally.
Powered by WPeMatico