You
must specify the appropriate DNS suffix for the Edge Transport server prior to its installation.
On the DNS servers that both the Edge Transport and Hub Transport servers are configured to
point to, configure host records in the appropriate forward lookup zones to resolve each server.
Alternatively, you can create host file entries on both the Edge Transport and Hub Transport
servers to resolve each other.
3. Send Connector to Internet: Create and configure a Send Connector to route outbound
Internet messages. The address space to be configured on this connector is * , which means it
can route messages to all Internet domains. It is typically configured to use DNS but can also
be configured to forward to a smart host such as an ISP or other third - party vendor. The usage
type for this connector is Internet. Figure 9 - 3 shows the creation of a new Send Connector for
this purpose. The source bridgehead will be the Edge Transport server; however, you do not
have to specify this in the New-SendConnector cmdlet. Whenever Send Connectors are
created on an Edge Transport server, the SourceTransportServers parameter should be
empty because the local Edge Transport server is always assumed as the Source bridgehead
server.
Part II: Working with Server Roles
246
Figure 9-3
The Edge Transport server will automatically be used as the source bridge head server
for this connector.
Pages:
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358