Quantcast
Channel: VMware Communities: Message List
Viewing all articles
Browse latest Browse all 240675

Re: External FQDN v.s. Internal FQDN

$
0
0

Hi pbjork,

 

In my case, where I am using different domain names for internal and external users, I am not sure that split DNS could help.

 

My external name is (example): gateway-va.ext_name.com, with public IP address, and external DNS resolving is working well.

My internal name is (example): gateway-va.int_name.local, with corporate IP address (private segment), and internal DNS resolving is working well.

 

So, If I must use same FQDN for both users, what could I do?

 

1. Could I configure external FQDN name, for both users, during initial setup, like: gateway-va.ext_name.com, and add A record to internal DNS server, for that FQDN (gateway-va,ext_name.com), to point to internal IP address of gateway-va VM, just to the same IP to which internal gateway name (gateway-va.int_name.local) is pointing? Is there any issues if FQDN is not within domain in which gateway-va is installed?

 

 

2. Is there any other way, like using external reverse proxy, which will be accessed by "external" name (gateway-va.ext_name.com), and forward all traffic toward internal name (gateway-va.int_name.local), and having FQDN that is configured with internal name (gateway-va.int_name.local)? BTW, I am not familiar with reverse proxy functionality.

 

 

Marcony


Viewing all articles
Browse latest Browse all 240675

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>