End reverse DNS lookups

One common complaint about Exchange is how slow it is, especially when dealing with Internet mail. The reality is, at least as far as Internet mail goes, much of the slowness may not be due to Exchange itself but with the way Exchange deals with DNS.

Whenever a piece of Internet mail is received or sent, Exchange performs a reverse DNS lookup on the recipient or sender (depending on the direction the mail is going in) and appends the results to the mail's "Received from:" header. The headers in question look something like this:

Received: from server3.com by server4.com; 27 Oct 96 15:27:39 PST
Received: from server2.com by server3.com; 27 May 02 15:15:13 PST
Received: from server1.com by server2.com; 27 May 02 15:01:59 PST
Date: 27 May 02 15:01:01 PST
From: henry@server1.com
Subject: Example headers
To: jerry@server2.com

Each one of these "Received:" headers is added at a different step during the mail delivery process, and each one involves a separate DNS lookup by a separate machine.

What is often overlooked is that DN...

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT Microsoft Exchange Server Mailbox Management Delivering email between Exchange server test and production domains Microsoft Outlook error message: 'Mailbox Size Limit exceeded' Restoring user accounts and mailbox links in Active Directory Problems receiving email from outside a Exchange Server 2003 domain Best practices for moving mailboxes in Exchange Server Exchange admins: Is it time to rethink your email address policy? Exchange Server 2003 collects email from only specific POP3 domains Troubleshoot 'System Attendant' error messages in OWA Relocating Outlook email messages on a hosted Exchange 2007 server Restore contacts from an Exchange public folder Exchange Server Administration Tips Remove Exchange 2003 objects from AD to install Exchange 2010 Is your Exchange 2007 hub transport server healthy? Avoid Outlook 2007 performance issues during repairs Developing an Exchange 2007 server role DR plan How DSAccess service improves Exchange Server 2007 reliability An introduction to the Exchange Remote Connectivity Analyzer tool Monitor Exchange 2007 with disk- and RPC-related counters DPM 2007 replica inconsistencies in Exchange databases Track Exchange 2007 mailbox server health using database counters Digging deeper into Exchange Server 2010

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary bounce e-mail  (SearchExchange.com) messaging server  (SearchExchange.com)

RELATED RESOURCES 2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems Search Bitpipe.com for the latest white papers and business webcasts Whatis.com, the online computer dictionary

S lookups are sometimes notoriously slow, especially if you are using a public DNS server or one inside your firewall that gets hammered a great deal. In truth, performing a DNS lookup on the addresses in the "Received:" line is not essential – all it does it provide a fully-qualified domain name rather than an IP address in that line. If you are experiencing slowness because of DNS lookups that take a long time to resolve, you may want to consider disabling reverse resolution lookup in Exchange. The main disadvantage of this is that your domain name will not appear in "Received:" headers; only the IP address of your mail server(s) will appear.

To disable reverse DNS in Exchange, open REGEDIT and locate the key:

HKEY_LOCAL_MACHINESystemCurrentControlSetServices MSExchangeIMCParameters

Add a new DWORD value named DisableReverseResolve and set it to 1. You'll need to restart Exchange before this takes effect.

Serdar Yegulalp is the editor of the Windows 2000 Power Users Newsletter.