Tip

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

    Requires Free Membership to View

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 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.


Do you have comments on this tip? Let us know.

This was first published in April 2005

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to:

Disclaimer: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.