Topic Last Modified: 2010-02-05

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:

Details

Product Name

Exchange

Product Version

14.0 (Exchange 2010)

Event ID

700

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

Sender ID agent: DNS isn't configured. Messages will temporarily be handled as if DNS requests have failed.

Explanation

This Error event indicates that there are no Domain Name System (DNS) servers configured in the TCP/IP configuration of the network adapter on the server. If Sender ID is enabled, Sender ID will continue to process messages based on the action configured on the Action tab of the Sender Id Properties dialog box. You can review the current Sender ID properties by selecting the Edge Transport node in the Exchange Management Console and then selecting Sender ID in the Anti-spam work pane.

For information about Sender ID actions and configuration, see the following:

  • Understanding Sender ID

  • Configure Sender ID Properties

User Action

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

  • Open a Command Prompt window, and then run ipconfig /all. Make sure that there is at least one DNS server listed in the properties of the network adapter. If no DNS server is listed in the network adapter properties, follow one of these steps:

    • If the server uses DHCP to obtain an IP address and a DNS server, try renewing the IP address lease. Open a command prompt and run ipconfig /renew. If unsuccessful, contact the DHCP administrator and have them correct the DHCP configuration.

    • If the server uses a statically assigned IP address, enter DNS records in the TCP/IP properties of the network adapter and run ipconfig /flushdns and ipconfig /registerdns at a command prompt.

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

  • If the previous steps do not resolve the problem:

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