Home
  •  

DNS 2008 Correct The Replication Problem Monitor

Microsoft.Windows.DNSServer.2008.Monitor.ServerConfiguration.CorrectReplicationProblem (UnitMonitor)

Knowledge Base article:

DNS Server Configuration

The DNS server configuration consists of the settings that determine how the DNS server will function on a network and how those settings are stored and retrieved when they are needed.

 

An attempt to update peer DNS servers with this server's new address failed (Cause)

 

Correct the replication problem (Resolution)

After updating its own host (A or AAAA) resource records, this server was not able to update its peer DNS servers that are integrated with Active Directory Domain Services (AD DS) by using dynamic update. As a result, this server will not be able to replicate with its peer DNS servers until their host resource records for this server are corrected.

This event can be logged even though this server has no replication partners, in which case it can be ignored. Otherwise, you should manually update the host resource records on one or more replication partners to ensure that the updated records will be replicated to all partners.

To perform this procedure, you must have membership in Domain Admins, or you must have been delegated the appropriate authority.

To ensure proper replication of this server's host records:

  1. On the DNS server, open Active Directory Sites and Services. To open Active Directory Sites and Services, click Start, click Administrative Tools, and then click Active Directory Sites and Services.
  2. In the console tree, expand the Sites container to display the list of sites.
  3. Double-click the site that contains the domain controller for which you want to determine Connection objects.

    Note: If you do not know the site in which the domain controller is located, open a command prompt, type ipconfig, and then press ENTER to get the IP address of the domain controller. Use the IP address to verify that an IP address maps to a subnet and to determine the site association.

  4. Expand the Servers folder to display the list of servers in that site.
  5. Expand the name of this server to display its NTDS settings.
  6. Double-click NTDS Settings to display the list of connection objects in the details pane. (These objects represent inbound connections that are used for replication.) The From Server column displays the names of the domain controllers that are the replication partners.
  7. Open DNS Manager. To open DNS Manager, click Start, click Administrative Tools, and then click DNS.
  8. In the console tree, right-click DNS, and then click Connect to DNS Server.
  9. Click The following computer, type the Domain Name System (DNS) name or IP address of one of the replication partners, and then click OK.
  10. In the console tree, expand the replication partner, expand Forward Lookup Zones, and then click the domain's zone.
  11. Right-click each host (A or AAAA) resource record for this server that contains an incorrect IP address, and then click Delete.
  12. If there are no remaining host records for this server, do the following:
    1. Right-click the domain's zone, and then click New Host (A or AAAA).
    2. In Name (uses parent domain if left blank), type the name of this server, and then in IP address, type an address for this server that the replication partner can contact. In other words, if this DNS server has multiple IP addresses, specify an address that is on the same network as the AD DS-integrated DNS server that you are updating.

Repeat step 12 to add additional host records for this server, and repeat steps 8 through 12 for other replication partners. Note that it is not necessary to update every replication partner. It is only necessary to correct the records on enough replication partners so that every server that replicates with this server will receive (through replication) the new data.

Element properties:

TargetMicrosoft.Windows.DNSServer.2008.Server
Parent MonitorSystem.Health.ConfigurationState
CategoryConfigurationHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.2SingleEventLog2StateMonitorType
RemotableTrue
AccessibilityInternal
Alert Message
DNS 2008 Replication Alert
{0}
RunAsMicrosoft.Windows.DNSServer.Library.ActionAccount

Source Code:

<UnitMonitor ID="Microsoft.Windows.DNSServer.2008.Monitor.ServerConfiguration.CorrectReplicationProblem" Accessibility="Internal" Enabled="onEssentialMonitoring" Target="Microsoft.Windows.DNSServer.2008.Server" ParentMonitorID="Health!System.Health.ConfigurationState" Remotable="true" Priority="Normal" RunAs="DNS!Microsoft.Windows.DNSServer.Library.ActionAccount" TypeID="Windows!Microsoft.Windows.2SingleEventLog2StateMonitorType" ConfirmDelivery="true">

  <Category>ConfigurationHealth</Category>

  <AlertSettings AlertMessage="Microsoft.Windows.DNSServer.2008.Monitor.ServerConfiguration.CorrectReplicationProblem_AlertMessageResourceID">

    <AlertOnState>Error</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/EventDescription$</AlertParameter1>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="UIGeneratedOpStateIdc7d6884b4fa6414287902408a47869bd" MonitorTypeStateID="FirstEventRaised" HealthState="Error"/>

    <OperationalState ID="UIGeneratedOpStateIdf485b4f9a0794de79409ba1f25f2f2ad" MonitorTypeStateID="SecondEventRaised" HealthState="Success"/>

  </OperationalStates>

  <Configuration>

    <FirstComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</FirstComputerName>

    <FirstLogName>DNS Server</FirstLogName>

    <FirstExpression>

      <And>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

              <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="UnsignedInteger">6702</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

              <XPathQuery Type="String">PublisherName</XPathQuery>

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="String">Microsoft-Windows-DNS-Server-Service</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

      </And>

    </FirstExpression>

    <SecondComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</SecondComputerName>

    <SecondLogName>DNS Server</SecondLogName>

    <SecondExpression>

      <And>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

              <XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="UnsignedInteger">7600</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

        <Expression>

          <SimpleExpression>

            <ValueExpression>

              <XPathQuery Type="String">PublisherName</XPathQuery>

            </ValueExpression>

            <Operator>Equal</Operator>

            <ValueExpression>

              <Value Type="String">Microsoft-Windows-DNS-Server-Service</Value>

            </ValueExpression>

          </SimpleExpression>

        </Expression>

      </And>

    </SecondExpression>

  </Configuration>

</UnitMonitor>