Free script for importing/exporting DNS information

Please let others know how useful this tip is via the rating scale at the end of it. Do you have a useful Exchange or Outlook tip, timesaver or workaround to share? Submit it to our tip contest and you could win a prize.

Exchange relies on DNS quite heavily. Many problems that are blamed on a broken Exchange configuration may in fact be caused by a misconfigured DNS server. If you're upgrading from an older Exchange installation to a newer one -- and migrating to a different DNS server along with it -- one possible way to determine if DNS problems are causing Exchange issues is to export a known-good DNS configuration to the target server.

Unfortunately, Windows has no built-in way to do this. This is doubly annoying if you have special DNS entries for your organization (for instance, if you have single-word DNS entries, also known as "single-label names") or other custom configurations that aren't easy to reproduce manually. Luckily, DNS guru Dean Wells has written a script called DNS Dump that helps get around this problem.

DNS Dump is a command-line batch file that imports and exports DNS information to a structured file, so you can move the DNS entries from site to site. The information exported includes DNS service...

Digg This!     StumbleUpon     Del.icio.us

RELATED CONTENT 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 Microsoft Exchange Server Administration Tools An introduction to the Exchange Remote Connectivity Analyzer tool Prevent Microsoft Outlook 2007 from hanging when forwarding email Testing Unified Messaging connectivity in Exchange 2007 Microsoft Exchange Server 2007 performance tutorial How to custom-configure a Microsoft Outlook 2007 install using OCT Top Exchange Server performance monitoring and troubleshooting tools Search and index Microsoft Outlook 2007 public folders Executing an .MSP customization file in Microsoft Outlook 2007 Using the NTBackup tool for Exchange Server backup and recovery Tools to bulk modify Active Directory users in Exchange Server 2003 Microsoft Exchange Server Administration Tools Research 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

RELATED GLOSSARY TERMS Terms from Whatis.com − the technology online dictionary Remote Installation Service  (SearchExchange.com) TCPMAN  (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

configuration, Active Directory-integrated zones and zone configuration data (which is important for Exchange), and conventional zone info. Existing AD zones will not be overwritten; however; you may need to manually erase existing AD zone information before running the tool. Non-AD zone information, however, will be erased and overwritten.

Note that DNS Dump can only import a file produced by the same version of DNS Dump. Also be sure to rename the file before you use it so it runs as a batch file -- the current file extension is .cm_ to keep it from being executed accidentally at download.

A side note: Windows Server doesn't require you to use the Microsoft DNS service. It certainly isn't the only choice out there; for instance, there are freeware implementations of the BIND service for Windows. But if you're troubleshooting Exchange issues because of DNS configuration problems and want to reduce the number of variables, it may be best to stick with Microsoft's DNS -- if only as a "better the devil you know" situation.

About the author: Serdar Yegulalp is editor of the Windows 2000 Power Users Newsletter and a regular contributor to SearchExchange.com.