We are trying to hit a client's web server by their internal name across a vpn. The name space they are insisting upon using is the same as their public namespace (ex: web1.abc.com). They are not going to publish this 'web1' record to their public DNS servers. I would normally use a dns rewrite or alias to have the public record returned as a private IP address so I can hit the 'web1' server across the vpn using the private IP's. But since they are not going to publish the name to the public DNS, how can I rewrite the response? It will come back as a non-existent host from the public DNS. The client isn't going to allow us to hit their internal DNS for name resolution nor will they allow us to create a secondary zone on our internal DNS servers.
It may not be a very scalable solution if you have many clients that will access this server, but you could add the server's private IP address to each of the client's hosts file. This way, the clients would resolve the server's name via the hosts file and not bother with DNS.
BenefitsDocumentationPrerequisiteImage Download LinksLimitationsSupported PlatformsLicense RequirementsTopologyStep-By-Step ConfigurationConfigure Virtual ServiceActivate the virtual service and configure guest IPsConfiguring UTD (Service Plane)Configurin...
Login to the FXOS chassis manager.
Direct your browser to https://hostname/, and log-in using the user-name and password.
Go to Help > About and check the current version:
Check the current version availa...
We have configured the outside and inside Interface with official ipv6 adresses, set a default route on outside Interface to our router, we also have definied a rule , which also gets hits, to permit tcp from inside Interface to any6.
In Syslog I also se...