Home
  •  

Microsoft Windows Server DNS Configuration Open Socket For Address

Microsoft.Windows.Server.DNS.Configuration.OpenSocketForAddress (Rule)

Alert generating rule for Configuration.

Knowledge Base article:

Summary

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.

Causes

The DNS server could not open socket for an address.

Resolutions

Correct server IP addresses and interfaces

The DNS server is configured to use an network interface that is not valid. You can either choose to allow the DNS server to use all the network interfaces that are installed on the server or you must confirm that the addresses of the selected interfaces are correct.

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

To correct the IP addresses that the DNS server is configured to use:

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

2.In the console tree, double-click Roles, double-click DNS Server, and then double-click DNS.

3.Right-click the DNS server, and then click Properties.

4.On the Interfaces tab, ensure that All IP addresses is selected, or determine whether any address in the IP addresses list is not valid for the server's network interfaces.

5.Clear the check box next to any invalid addresses, and then click OK.

6.Right-click the DNS server, click All Tasks, and then click Restart.

If this was the only IP interface on this computer, the DNS server might not restart as a result of this error. In that case, remove the DNS\Parameters\ListenAddress value in the services section of the registry, and then restart the DNS Server service.

To remove the DNS\Parameters\ListenAddress value in the registry:

Caution: Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

1.On the DNS server, start Registry Editor. To start Registry editor, click Start, click Run, type regedit, and then click OK.

2.In the console tree, navigate to the following key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters

3.Right-click ListAddresses, and then click Delete.

4.In Server Manager, right-click the DNS server, click All Tasks, and then click Restart.

If all the IP addresses for this computer are valid, make sure that no other application (such as a third-party DNS server) is running that might try to use the Domain Name System (DNS) port.

External

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

Element properties:

TargetMicrosoft.Windows.Server.DNS.Server
CategoryAlert
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
RemotableTrue
Alert Message
Windows DNS - Configuration - Open Socket For Address

Event ID: {0}
Event Source: {1}
Event Log: {2}

Event Description: {3}
Event LogDNS Server

Member Modules:

ID Module Type TypeId RunAs 
DS DataSource Microsoft.Windows.EventProvider Default
Alert WriteAction System.Health.GenerateAlert Default

Source Code:

<Rule ID="Microsoft.Windows.Server.DNS.Configuration.OpenSocketForAddress" Enabled="true" Target="Microsoft.Windows.Server.DNS.Server" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">

  <Category>Alert</Category>

  <DataSources>

    <DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">

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

      <LogName>DNS Server</LogName>

      <Expression>

        <SimpleExpression>

          <ValueExpression>

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

          </ValueExpression>

          <Operator>Equal</Operator>

          <ValueExpression>

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

          </ValueExpression>

        </SimpleExpression>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="Alert" TypeID="Health!System.Health.GenerateAlert">

      <Priority>1</Priority>

      <Severity>2</Severity>

      <AlertOwner/>

      <AlertMessageId>$MPElement[Name="Microsoft.Windows.Server.DNS.Configuration.OpenSocketForAddress.AlertMessage"]$</AlertMessageId>

      <AlertParameters>

        <AlertParameter1>$Data/EventDisplayNumber$</AlertParameter1>

        <AlertParameter2>$Data/EventSourceName$</AlertParameter2>

        <AlertParameter3>$Data/Channel$</AlertParameter3>

        <AlertParameter4>$Data/EventDescription$</AlertParameter4>

      </AlertParameters>

      <Suppression>

        <SuppressionValue>$Data/LoggingComputer$</SuppressionValue>

      </Suppression>

      <Custom1/>

      <Custom2/>

      <Custom3/>

      <Custom4/>

      <Custom5/>

      <Custom6/>

      <Custom7/>

      <Custom8/>

      <Custom9/>

      <Custom10/>

    </WriteAction>

  </WriteActions>

</Rule>