These parameters do not apply to the Edge Transport server. The Identity parameter always returns the
local Edge Transport server and the domain controller parameter is not supported on the Edge Transport
server because it is installed in a perimeter network with no access to Active Directory on a domain
controller. Figures 7 - 5 and 7 - 6 display all the transport server settings available on the Hub Transport
server.
The following section takes a quick look at a couple of the settings.
DNS Configuration
By default if InternalDNSAdapterEnabled is set to True , the Hub Transport server will always
use the DNS servers configured on the internal network adapter. This is also the case even if
ExternalDNSAdapterEnabled is True . If InternalDNSAdapterEnabled is set to False and DNS
servers are manually specified, then the servers listed in the InternalDNSServers parameter will
always be used. The Hub Transport only uses DNS servers specified with the ExternalDNSServers
parameter or the external network adapter when a Send Connector is configured to use it.
In Figure 7 - 5 , notice that both InternalDNSAdapterEnabled and ExternalDNSAdapterEnabled
parameters are set to True on the transport server. This is the case even if the server is configured
with a single network card. The DNS server(s) specified on the network card is used.
Pages:
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301