DNS lookups are used by Exchange 2007 transport servers to resolve a host name to an IP address. Make sure that the server is configured to enable DNS resolution for hosts inside the Active Directory directory service forest and hosts that are outside the Exchange organization. The configuration of the transport server controls the DNS server that is queried to resolve an individual lookup. The transport server properties can be configured to use the DNS server configuration of a local network adapter. The transport server properties can also be configured to query a specific DNS server for host name resolution. If the transport server has more than one network adapter, you can configure DNS lookup to use the configuration of a specific network adapter for external and internal DNS lookups.

DNS lookups are directed to a particular DNS server as follows:

• By default, the DNS configuration of a network adapter is selected. To override use of the network adapter configuration, by using the Set-TransportServer cmdlet in the Exchange Management Shell, you must set the InternalDNSAdapterEnabled and ExternalDNSAdapterEnabled parameters to $False and configure a list of DNS servers to query. You can also use the Exchange Management Console to modify this configuration.
  
  
• The configuration of internal DNS Lookups is used by default.
  
  
• The configuration of external DNS lookups is used only when a Send connector is configured to use these settings. This setting is enabled on a per-connector basis.
  
  
• If you configure more than one DNS server address, the first DNS server listed is considered the primary DNS server. Additional entries are considered secondary DNS servers. Secondary DNS servers are queried only when the primary DNS server can't be reached.
  
  
• If you configure DNS lookups to use the DNS server configuration of a specific network adapter, you must specify the adapter by its GUID. Never apply the network adapter GUID of one server to the transport settings of another server. If you do this, the server can't send mail because it can't locate the network adapter that is referenced by the GUID.
  
  
• To retrieve the GUID for a network adapter, run the Get-NetworkConnectionInfo cmdlet in the Exchange Management Shell. This cmdlet must be run locally on the computer for which you want to retrieve the network adapter GUID. The following example shows the output of the Get-NetworkConnectionInfo cmdlet.
  
  

	Copy Code
[PS] D:\Documents and Settings\Administrator>Get-NetworkConnectionInfo Name : Intel(R) PRO/1000 MT Network Connection DnsServers : {10.197.12.19, 10.197.12.20} IPAddresses : {10.197.21.53} AdapterGuid : 0d372140-eae6-4350-9ef8-14d9d10061f2 MacAddress : 00:0B:DB:4E:8C:A6

Note:

If Exchange 2007 SP1 is deployed on a computer that is running Windows Server 2008, you can enter IP addresses and IP address ranges in the Internet Protocol Version 4 (IPv4) format, Internet Protocol Version 6 (IPv6) format, or both formats. A default installation of Windows Server 2008 enables support for IPv4 and IPv6. For more information about Exchange 2007 SP1 support for IPv6 addresses, see IPv6 Support in Exchange 2007 SP1 and SP2.

External DNS Lookups

Internal DNS Lookups

The Limits tab of the transport server properties or the Set-TransportServer cmdlet is used to configure the following settings:

• Retries   These settings determine the interval at which an Exchange 2007 transport server will retry message delivery when a connection failure occurs. The available settings are as follows:
  
  
  • Outbound connection failure retry interval (minutes)   Use this field to specify the retry interval for subsequent connection attempts to a remote server where earlier connections have failed. The previously failed connection attempts are controlled by the value of Transient failure retry attempts and the Transient failure retry interval. On a Hub Transport server, the default value is 10 minutes. On an Edge Transport server, the default value is 30 minutes. The valid input range is 1 minute to 28,800 minutes (20 days). The corresponding parameter in the Set-TransportServer cmdlet is OutboundConnectionFailureRetryInterval.
    
    
  • Transient failure retry interval (seconds)   Use this field to specify the connection interval between each connection attempt that is specified by the value of Transient failure retry attempts. On a Hub Transport server, the default value is 5 minutes. On an Edge Transport server, the default value is 10 minutes. The valid input range is 1 second to 43,200 seconds (12 hours). The corresponding parameter in the Set-TransportServer cmdlet is TransientFailureRetryInterval.
    
    
  • Transient failure retry attempts   Use this field to specify the maximum number of times that a server immediately retries when it encounters a connection failure with a remote server. The default value is 6. The valid input range is 0 to 6. When this parameter is set to 0, the server doesn't immediately try to reconnect. The corresponding parameter in the Set-TransportServer cmdlet is TransientFailureRetryCount.
    
    
• Message expiration   This setting determines how long an Exchange 2007 transport server tries to deliver a message before the server removes the message from the queue. If a message remains in the queue for more time, the message is returned to the sender as a hard failure. The default value is 2 days. The valid input range is 1 day to 90 days. The corresponding parameter in the Set-TransportServer cmdlet is MessageExpirationTimeout.
  
  
• Notifications   This setting is used to determine how long the server waits before it generates a delivery status notification (DSN) to the sender about a delivery delay. The default value is 4 hours. The valid input range is 1 hour to 720 hours (30 days). The value of Notifications should always be greater than the value of the Transient failure retry interval multiplied by the value of Transient failure retry attempts. The corresponding parameter in the Set-TransportServer cmdlet is DelayNotificationTimeout.
  
  
• Connection restrictions   These settings limit the maximum number of concurrent connections that can exist on an Exchange 2007 transport server. You can configure an overall limit. You can also configure a per domain limit. The available settings are as follows:
  
  
• Maximum concurrent outbound connections   Select this option to specify the maximum number of outbound connections that can be open at a time. If the connection limit is reached, the server does not initiate new connections until the number of current connections decreases. The default value is 1000. The valid input range is 1 to 2147483647. If you clear the checkbox next to Maximum concurrent outbound connections, no limit is imposed on the number of concurrent outbound connections. The value of Maximum concurrent outbound connections must be greater than or equal to the value of Maximum concurrent outbound connections per domain. The corresponding parameter in the Set-TransportServer cmdlet is MaxOutboundConnections.
  
  
• Maximum concurrent outbound connections per domain   Select this option to specify the maximum number of concurrent connections to any single domain. The default value is 20. The valid input range is 1 to 2147483647. If you clear the checkbox next to Maximum concurrent outbound connections per domain, no limit is imposed on the number of concurrent outbound connections per domain. The value of Maximum concurrent outbound connections per domain must be less than or equal to the value of Maximum concurrent outbound connections. The corresponding parameter in the Set-TransportServer cmdlet is MaxPerDomainOutboundConnections.
  
  

Figure 8 shows the default configuration of the Limits tab for a Hub Transport server. The Limits tab is the same in Exchange 2007 RTM and in Exchange 2007 SP1.

For more information about how to configure these properties, see Managing Message Retry, Resubmit, and Expiration Intervals.

Transport Server Log Settings

The Log Settings tab of the transport server properties or the Set-TransportServer cmdlet is used to configure the following transport log settings:

Note:
In Exchange 2007 RTM, there is no Log Settings tab in the transport server properties. You must use the Set-TransportServer cmdlet in the Exchange Management Shell to configure the transport server log settings.

• Message tracking log   These settings control the state of message tracking and the location of the message tracking logs. The message tracking log is a detailed log of all message activity as messages are transferred to and from a computer that is running Exchange. Message tracking is available on Hub Transport servers, Edge Transport servers, and Mailbox servers. The message tracking settings that are available in the Exchange Management Console are as follows:
  
  
  • Enable message tracking log   By default, message tracking is enabled on a Hub Transport servers and Edge Transport servers. To disable message tracking, clear the checkbox next to Enable message tracking log. To enable message tracking, select the checkbox next to Enable message tracking log. The corresponding parameter in the Set-TransportServer cmdlet is MessageTrackingLogEnabled.
    
    
  • Message tracking log path   This field displays the current location of the message tracking logs. To change the location of the message tracking logs, message tracking must be enabled. Click Browse next to Message tracking log path. In the Browse for folder window, browse to the new location where you want to store the message tracking log files. If you want to create a new folder, select a parent folder, click Make New Folder, and then type the name of the new folder. After you make your folder selection, click OK to close the Browse for folder window. The corresponding parameter in the Set-TransportServer cmdlet is MessageTrackingLogPath.
    
    
  All other message tracking log settings can only be configured by using the Set-TransportServer cmdlet in the Exchange Management Shell. For more information, see How to Configure Message Tracking.
  
  
• Connectivity log   These settings control the state of connectivity logging and the location of the connectivity logs. The connectivity log is a record of the Simple Mail Transfer Protocol (SMTP) connection activity of the outbound message delivery queues to the destination Mailbox server, smart host, or domain. The available connectivity log settings in the Exchange Management Console are as follows:
  
  
  • Enable connectivity log   By default, connectivity logging is disabled on Hub Transport servers and Edge Transport servers. To enable connectivity logging, clear the checkbox next to Enable connectivity log. To enable connectivity logging, select the checkbox next to Enable connectivity log. The corresponding parameter in the Set-TransportServer cmdlet is ConnectivityLogEnabled.
    
    
  • Connectivity log path   This field displays the current location of the connectivity logs. To change the location of the connectivity logs, connectivity logging must be enabled. Click Browse next to Connectivity log path. In the Browse for folder window, browse to the new location where you want to store the connectivity log files. If you want to create a new folder, select a parent folder, click Make New Folder, and then type the name of the new folder. After you make your folder selection, click OK to close the Browse for folder window. The corresponding parameter in the Set-TransportServer cmdlet is ConnectivityLogPath.
    
    
  All other connectivity log settings can only be configured by using the Set-TransportServer cmdlet in the Exchange Management Shell. For more information, see How to Configure Connectivity Logging.
  
  
• Protocol log   These settings control the location of the protocol logs. A protocol log is a record of the SMTP activity between messaging servers as part of message delivery. This SMTP activity occurs on Send connectors and Receive connectors that are configured on Hub Transport servers and Edge Transport servers. By default, protocol logging is disabled. The protocol log settings in the Exchange Management Console are as follows:
  
  
  • Send connector protocol log path   This field displays the current location of the Send connector protocol logs. All of the Send connectors that are configured on the Hub Transport server or Edge Transport server share the same protocol logs. By default, protocol logging is disabled on all Send connectors. You can enable or disable protocol logging on each Send connector by using the Set-SendConnector cmdlet in the Exchange Management Shell, or in the properties of the Send connector in the Exchange Management Console.
    
    To change the location of the Send connector protocol logs, click Browse next to Send connector protocol log path. In the Browse for folder window, browse to the new location where you want to store the Send connector protocol log files. If you want to create a new folder, select a parent folder, click Make New Folder, and then type the name of the new folder. After you make your folder selection, click OK to close the Browse for folder window. The corresponding parameter in the Set-TransportServer cmdlet is SendProtocolLogPath.
    
    
  • Receive connector protocol log path   This field displays the current location of the Receive connector protocol logs. All of the Receive connectors that are configured on the Hub Transport server or Edge Transport server share the same protocol logs. By default, protocol logging is disabled on all Receive connectors. You can enable or disable protocol logging on each Receive connector by using the Set-ReceiveConnector cmdlet in the Exchange Management Shell, or in the properties of the Receive connector in the Exchange Management Console.
    
    To change the location of the Receive connector protocol logs, click Browse next to Receive connector protocol log path. In the Browse for folder window, browse to the new location where you want to store the Receive connector protocol log files. If you want to create a new folder, select a parent folder, click Make New Folder, and then type the name of the new folder. After you make your folder selection, click OK to close the Browse for folder window. The corresponding parameter in the Set-TransportServer cmdlet is ReceiveProtocolLogPath.
    
    
  Other than enabling or disabling protocol logging, all other protocol log settings can only be configured by using the Set-TransportServer cmdlet in the Exchange Management Shell. For more information, see How to Configure Protocol Logging.
  
  

Figure 9 shows the Log Settings tab for the Hub Transport server properties in Exchange 2007 SP1.

When you change the location of the message tracking log directory, the connectivity log directory, the Send connector protocol log directory, or the Receive connector protocol log directory, this change does not copy any existing log files from the old directory to the new directory. The new log directory is active almost immediately after the configuration change, but any existing log files are left in the old directory.

The following permissions are required on the log directory:

• Administrator: Full Control
  
  
• System: Full Control
  
  
• Network Service: Read, Write, and Delete Subfolders and Files
  
  

By default, the Exchange Transport service uses the security credentials of the Network Service user account to create the log directory and apply the correct permissions. If the new log directory does not already exist, and the Network Service account has the rights that are required to create folders and apply permissions at the new location, the new log directory is created and the correct permissions are applied to the new directory. If the log directory already exists, the existing folder permissions are not checked. Whenever you move the log directory, it is always a good idea to verify the log directory and to verify that the new directory has the correct permissions applied to it.

Additional Transport Server Settings

When you use the Exchange Management Shell to configure the transport server, you can modify additional properties that are unavailable in the Exchange Management Console. These properties control settings that relate to the following transport features:

• Delivery status notifications
  
  
• External Postmaster address
  
  
• Connection rates
  
  
• Pickup directory
  
  
• Pipeline tracing
  
  
• Poison messages
  
  
• Replay directory
  
  
• Routing table logging
  
  

For more information about how to modify these properties by using cmdlets in the Exchange Management Shell, see the following topics: 

• Set-TransportServer
  
  
• Get-TransportServer
  
  

For More Information

For more information, see the following topics:

• Get-ExchangeServer
  
  
• Configuring DNS Settings for Exchange 2007 Servers
  
  
• Managing Message Retry, Resubmit, and Expiration Intervals
  
  
• Managing Connectors
  
  
• Managing the Pickup Directory
  
  
• Managing the Replay Directory
  
  
• Managing Delivery Status Notifications
  
  
• Managing Message Tracking
  
  
• Managing Protocol Logging
  
  
• Managing Connectivity Logging
  
  
• Managing Routing Table Logging
  
  

To ensure that you are reading the most up-to-date information and to find additional Exchange Server 2007 documentation, visit the Exchange Server TechCenter.

---

© 2008 Microsoft Corporation. All rights reserved. Legal Information

---

• Перевести на английский

Figure 9   Log Settings tab for the Hub Transport server properties in Exchange 2007 SP1

Figure 8  Limits tab for a Hub Transport server