Forum Discussion
Brad_Parker
Cirrus
Your wideIP should resolve public IPs for the virtual servers to receive traffic from the internet. Thos public IPs can either live on the virtual servers themselves(preferred) or can be NAT's upstream by a firewall or some other device. If you make you virtual servers with public IPs directly GTM and "auto discover" the virtual servers automatically rather than having to manually create the virtual server in the GTM context.
Brad_Parker
Nov 03, 2015Cirrus
Technically you could get away with the 1 public as HTTP/S and DNS run on different ports, but its more of a question if you want that traffic on the same IP address. Also, you say you have 2 sites, if they are both HTTPS that will require you to use SNI. While you can get away with this 1 public IP approach, most don't do this. One reason is rDNS. Reverse DNS can only point to one FQDN and I assumer the name of your NS records will be different than your sites.