Even
though the Edge Server will not be installed in your domain, it does require a DNS record,
as shown in Figure 5.2.
Figure 5.2 Internal DNS Record for the Edge Server
Obtaining Public IP Addresses
Each of your three FQDNs needs a publicly routable IP address, because external users will
be accessing all three external services: Access Edge, A/V Edge, and Web Conferencing Edge.
Your Internet service provider (ISP) assigns these publicly routable IP addresses. In most
networks, the public IP addresses typically will terminate on your fi rewall.
Some people have complained that the Edge Server requires too many public IP addresses,
too many FQDNs, and consequently, too many Secure Sockets Layer (SSL) certifi cates. You
could use just one FQDN and public IP address for all three Edge services, but I don??™t
140 Chapter 5 ??? Confi guring the Edge Server
recommend this unless you really have a good grasp of the Transmission Control Protocol/
Internet Protocol (TCP/IP), OCS, certifi cates, and fi rewalls. Departing from the default ports
requires you to change these port numbers in several locations, making your deployment more
complex than it needs to be. It becomes diffi cult to troubleshoot when you aren??™t sure which
ports are supposed to be in use and which are not.
Why all the fuss? Under normal circumstances, using a single IP address would create
TCP port confl icts. All three of the Edge services use TCP port 443; if you are using only
on IP address, you can??™t have multiple services using the same port.
Pages:
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198