Microsoft Windows Server DNS Auto configuration Failed

Microsoft.Windows.Server.DNS.Autoconfig.Failed (UnitMonitor)

Warning indicates a 2630 event. Health is reset by a 2631 event.

Knowledge Base article:

Summary

When a DNS server is installed as part of the process of creating a domain controller, it is configured automatically to use the appropriate DNS servers for name resolution, forwarding, and root hints.

Causes

The DNS server could not configure the network connections of this computer with the local computer's IP address as the preferred DNS server, because this computer is connected to networks with different or invalid DNS namespaces.

Resolutions

Correct the DNS server configuration

When the DNS Server role is configured to integrate with Active Directory Domain Services (AD DS), the TCP/IP settings of the server are configured to use the local DNS server as the preferred DNS server. This auto configuration process has failed, leaving the server in an inconsistent state. To correct this condition, you must ensure that the server is configured to use itself as the preferred DNS server and that the server is properly configured to work with AD DS. Your Active Directory infrastructure will not function properly until this issue is resolved.

Ensure that the network connections of the DNS server are configured with its own IP address as the preferred DNS server.

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

To view and set the preferred DNS server:

1.On the DNS server, click Start, right-click Network, and then click Properties.

2.In the Network and Sharing Center, click Manage network connections.

3.In Network Connections, right-click a connection, and then click Properties.

4.Click the appropriate Internet Protocol version for your environment, and then click Properties.

5.Verify that Use the following DNS server addresses is selected and that Preferred DNS server contains the IP address of this server. If necessary, replace the IP address with the IP address of this server.

Ensure that the domain-controller locator DNS records that are enumerated in the file %systemroot%\system32\config\netlogon.dns are registered on the local DNS server.

To view records in the netlogon.dns file:

1.On the DNS server, click Start, and then click Run.

2.Type notepad %systemroot%\system32\config\netlogon.dns, and then click OK.

The file should contain records similar to the following:

Domain. 600 IN A 157.59.85.147 _ldap._tcp.Domain. 600 IN SRV 0 100 389 Server.Domain.

_ldap._tcp.Default-First-Site-Name._sites.Domain. 600 IN SRV 0 100 389 Server.Domain.

Where Domain is the fully qualified name of the domain, and Server is the unqualified name of the DNS server (domain controller).

If these records are not registered, do the following:

- Add a delegation to this DNS server to the parent DNS zone that matches the name of the Active Directory domain.

- Configure the local DNS server with appropriate root hints and forwarders, if necessary.

To add a delegation to this DNS server:

1.On the DNS server, open DNS Manager. To open DNS Manager, click Start, click Administrative Tools, and then click DNS.

2.In the console tree, right-click DNS, and then click Connect to DNS Server.

3.Click The following computer, type the DNS name or IP address of the DNS server hosting the parent zone, and then click OK.

4.In the console tree, right-click the parent domain, and then click New Delegation.

5.Follow the instructions in the New Delegation Wizard to finish creating the new delegated domain.

To configure this DNS server with root hints and forwarders:

1.On the DNS server, open DNS Manager. To open DNS Manager, click Start, click Administrative Tools, and then click DNS.

2.In the console tree, right-click the DNS server, and then click Properties.

3.Click the Root Hints tab, and then modify server root hints as follows:

- To add a root server to the list, click Add, and then specify the name and IP address of the server to be added to the list.

- To modify a root server in the list, click Edit, and then specify the name and IP address of the server to be modified in the list.

- To remove a root server from the list, select it in the list, and then click Remove.

- To copy root hints from a DNS server, click Copy from server, and then specify the IP address of the DNS server from which you want to copy a list of root servers to use in resolving queries. These root hints will not overwrite any existing root hints.

4.Click the Forwarders tab, and then click Edit.

5.Modify the forwarders list as follows:

- To add a forwarder, type the IP address or DNS name of the forwarder.

- To modify a forwarder, click the forwarder, and then type a new IP address or DNS name.

- To remove a forwarder, click the forwarder, and then click Delete.

External

http://technet.microsoft.com/en-us/library/dd349718(v=ws.10).aspx

Element properties:

TargetMicrosoft.Windows.Server.DNS.Server
Parent MonitorSystem.Health.ConfigurationState
CategoryConfigurationHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityWarning
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.2SingleEventLog2StateMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
Windows DNS - Auto configuration Failed

This alert is generated by event 2630 in the DNS Server event log, and cleared by event 2631.

Please see Health Explorer for details.

Event Description: {0}
RunAsMicrosoft.Windows.Server.DNS.ActionAccount

Source Code:

<UnitMonitor ID="Microsoft.Windows.Server.DNS.Autoconfig.Failed" Accessibility="Public" Enabled="true" Target="Microsoft.Windows.Server.DNS.Server" ParentMonitorID="Health!System.Health.ConfigurationState" Remotable="true" Priority="Normal" RunAs="Microsoft.Windows.Server.DNS.ActionAccount" TypeID="Windows!Microsoft.Windows.2SingleEventLog2StateMonitorType" ConfirmDelivery="true">
<Category>ConfigurationHealth</Category>
<AlertSettings AlertMessage="Microsoft.Windows.Server.DNS.Autoconfig.Failed_AlertMessageResourceID">
<AlertOnState>Warning</AlertOnState>
<AutoResolve>true</AutoResolve>
<AlertPriority>Normal</AlertPriority>
<AlertSeverity>Warning</AlertSeverity>
<AlertParameters>
<AlertParameter1>$Data/Context/EventDescription$</AlertParameter1>
</AlertParameters>
</AlertSettings>
<OperationalStates>
<OperationalState ID="FirstEventRaised" MonitorTypeStateID="FirstEventRaised" HealthState="Warning"/>
<OperationalState ID="SecondEventRaised" MonitorTypeStateID="SecondEventRaised" HealthState="Success"/>
</OperationalStates>
<Configuration>
<FirstComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</FirstComputerName>
<FirstLogName>DNS Server</FirstLogName>
<FirstExpression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">2630</Value>
</ValueExpression>
</SimpleExpression>
</FirstExpression>
<SecondComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</SecondComputerName>
<SecondLogName>DNS Server</SecondLogName>
<SecondExpression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">2631</Value>
</ValueExpression>
</SimpleExpression>
</SecondExpression>
</Configuration>
</UnitMonitor>