Topic Last Modified: 2010-02-10

The Microsoft Exchange Server 2010 Management Pack for System Center Operations Manager monitors the Windows Application log on computers running Exchange 2010 and generates this alert when the events specified in the following Details table are logged.

To learn more about this alert, in Operations Manager, do one or more of the following:

From the Operations Console, double-click this alert, and then click the General tab. Review the description of the alert that includes the variables specific to your environment.
From the Operations Console, double-click this alert, and then click the Alert Context tab. Review the logged events that meet the criteria of this Operations Manager alert.

Details

Product Name	Exchange
Product Version	14.0 (Exchange 2010)
Event ID	101
Event Source	MSExchange Antispam
Alert Type	Warning
Rule Path	Microsoft Exchange Server/Exchange 2010/Common Components/Hub Transport and Edge Transport/Agents/Common
Rule Name	Protocol Analysis: DNS is not configured. Most likely, the reason for this is that no DNS servers were found. Sender Reputation calculations are disabled.

Explanation

This Error event indicates that the server cannot access a Domain Name System (DNS). Both sender reputation calculation and the ability to add items to the block list require that name resolution be configured and functional.

For information about sender reputation, see:

Understanding Sender Reputation

User Action

To resolve this problem, follow one or more of these steps:

Review the Application log and System log on your Exchange 2010 servers for related events. For example, events that occur immediately before and after this event may provide more information about the root cause of this error.
Make sure that the DNS configuration is accurate:
1. Use the command prompt command ipconfig /all to verify that the DNS information is correct.
2. If needed, refresh the DNS cache on the server. Enter ipconfig /flushdns and then ipconfig /registerdns at a command prompt to clear the DNS cache and refresh the DNS lease and reregister the DNS name.
3. Verify the DNS information is correct by entering ipconfig /all at a command prompt.
Make sure that the server that runs Exchange Server 2010 can ping the DNS server.
Resolve your issue by using self-support options, assisted support options, and other resources. You can access these resources from the Exchange Server Solutions Center. From this page, click Self-Support Options in the navigation pane to use self-help options. Self-help options include searching the Microsoft Knowledge Base, posting a question at the Exchange Server forums, and others. Alternatively, in the navigation pane, you can click Assisted Support Options to contact a Microsoft support professional. Because your organization may have a specific procedure for directly contacting Microsoft Technical Support, be sure to review your organization's guidelines first.

For More Information

If you are not already doing so, consider running the Exchange tools created to help you analyze and troubleshoot your Exchange environment. These tools can help make sure that your configuration aligns with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. To run these tools, go to the Toolbox node of the Exchange Management Console. To learn more about these tools, see Managing Tools in the Toolbox.