Home
  •  

Core Service Domain Name Problems

Core_Service_Domain_Name_Problems_1_Rule (Rule)

Knowledge Base article:

Management Pack
Summary

The DNS server has encountered an error while loading a zone file. Although the DNS server will continue to load even if it encounters errors in a zone file, it is strongly recommended that you correct any problems found in a zone file.
This alert is triggered when the Windows 2000 DNS server generates one of the following DNS event IDs:

1541, 1542, 1543, 1544, 1545, 1546, 1547

  • For each event ID, see Causes for information about the specific cause of the failure.
  • See Resolutions for information about the specific steps you can take to resolve the failure and restore the functionality of the DNS server.
 
Causes

Possible causes of this problem include:

  • 1540 The DNS server was unable to create a domain node, as described in the event log data.

  • 1541. The DNS server encountered an invalid domain name in a zone file, as described in the event log data.

  • 1542. The DNS server encountered an invalid domain name, as described in the event log data.
  • 1543. The DNS server encountered a domain name exceeding the maximum allowable length.
  • 1544. The DNS server encountered an invalid token in a zone file, as described in the event log data.
  • 1545. The DNS server encountered a name outside of the specified zone in a zone file, as described in the event log data.
  • 1546. The DNS server encountered an invalid name server (NS) resource record in a zone file, as described in the event log data. (The use of NS resource records (RR) must be at either the zone root node or be placed at the sub-zone context within the zone for a domain being delegated away from this zone.)
  • 1547. The DNS server encountered an invalid host (A) resource record in a zone file, as described in the event log data. The use of A resource records (RRs) must be at a domain name within the zone, with the exception of glue A RRs which are used to resolve the host name specified in an NS RR also contained at the same domain node and used for a zone delegation.
 
Resolutions

If the DNS server encounters invalid information (domain name, token, resource record) in a zone file, the DNS server will continue to load. However, it is strongly recommended that you either correct or remove the invalid information from the zone file, using the DNS MMC snap-in.

1. Open the DNS MMC snap-in. To open the DNS MMC snap-in, click Start, click Control Panel, double-click Administrative Tools, and then double-click DNS.
2. In the console tree, click the applicable DNS server.
3. In the console tree, click the applicable zone.
4. In the details pane, fix or delete the invalid zone information. 

For detailed information about the location and identity of the invalid information, refer to the event log data.
 
Sample Event

1540 (Error) SymbolicName=DNS_EVENT_DOMAIN_NODE_CREATION_ERROR

The DNS server unable to create domain node.

1541 (Error) SymbolicName=DNS_EVENT_PARSED_INVALID_DOMAIN_NAME

The DNS server encountered invalid domain name "%1" in zone file %2 at line %3. Although the DNS server continues to load, ignoring this name, it is strongly recommended that you either correct the name or remove the resource record from the zone file, which is located in the %SystemRoot%\System32\Dns folder.

1542 (Error) SymbolicName=DNS_EVENT_INVALID_DOTTED_DOMAIN_NAME

The DNS server encountered invalid domain name "%1".

1543 (Error) SymbolicName=DNS_EVENT_DOMAIN_NAME_TOO_LONG

The DNS server encountered domain name "%1" exceeding maximum length. Although the DNS server continues to load, ignoring this name, it is recommended that you either correct the name or remove the resource record from the zone file, which is located in the %SystemRoot%\System32\Dns folder.

1544 (Error) SymbolicName=DNS_EVENT_INVALID_ORIGIN_TOKEN

The DNS server encountered an invalid "@" token "%1" in zone file %2 at line %3. Although the DNS server continues to load, ignoring this token, it is recommended that you either correct the token or remove the resource record from the zone file. The zone file is located in the %SystemRoot%\System32\Dns folder.

1545 (Error) SymbolicName=DNS_EVENT_FILE_NODE_OUTSIDE_ZONE

The DNS server encountered a name outside of the specified zone in zone file %1 at line %2. Although the DNS server continues to load, ignoring this resource record (RR), it is recommended that you either correct the RR or remove it from the zone file, which is located in the %SystemRoot%\System32\Dns folder.

1546 (Error) SymbolicName=DNS_EVENT_FILE_INVALID_NS_NODE

The DNS server encountered an invalid name server (NS) resource record in zone file %1 at line %2. The use of NS resource records (RR) must be at either the zone root node or be placed at the sub-zone context within the zone for a domain being delegated away from this zone. Although the DNS server continues to load, ignoring this RR, it is recommended that you either correct the RR or remove it from the zone file. The zone file is located in the %SystemRoot%\System32\Dns folder. For more information, see "Delegating zones" in the online Help.

1547 (Error) SymbolicName=DNS_EVENT_FILE_INVALID_A_NODE

The DNS server encountered an invalid host (A) resource record in zone file %1 at line %2. The use of A resource records (RRs) must be at a domain name within the zone, with the exception of glue A RRs which are used to resolve the host name specified in an NS RR also contained at the same domain node and used for a zone delegation. Although the DNS server continues to load, ignoring this RR, it is strongly recommended that you either correct this RR or remove it from the zone file. The zone file is located in the %SystemRoot%\System32\Dns folder. For more information, see "Delegating zones" in the online Help.
 
© 2000-2004 Microsoft Corporation, all rights reserved.

Element properties:

TargetMicrosoft.Windows.Server.DNS.Microsoft_Windows_2000_DNS_Servers_Installation
CategoryEventCollection
EnabledTrue
Event SourceDNS
Alert GenerateTrue
Alert SeverityError
Alert PriorityLow
RemotableTrue
Alert Message
Core Service Domain Name Problems

$Data/EventDescription$
Event LogDNS Server
CommentMom2005ID='{F73C3F09-7AED-4887-9F4E-D20AEACF1FD2}';MOM2005ComputerGroupID={1C77A494-F086-4C7B-9469-5713AD1B5FAC}

Member Modules:

ID Module Type TypeId RunAs 
_907D4570_146C_11D3_AB21_00A0C98620CE_ DataSource Microsoft.Windows.EventProvider Default
CollectEventData WriteAction Microsoft.SystemCenter.CollectEvent Default
CollectEventDataWarehouse WriteAction Microsoft.SystemCenter.DataWarehouse.PublishEventData Default
GenerateAlert WriteAction System.Mom.BackwardCompatibility.AlertResponse Default

Source Code:

<Rule ID="Core_Service_Domain_Name_Problems_1_Rule" Comment="Mom2005ID='{F73C3F09-7AED-4887-9F4E-D20AEACF1FD2}';MOM2005ComputerGroupID={1C77A494-F086-4C7B-9469-5713AD1B5FAC}" Enabled="true" Target="Microsoft.Windows.Server.DNS.Microsoft_Windows_2000_DNS_Servers_Installation" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">

  <Category>EventCollection</Category>

  <DataSources>

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

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

      <LogName>DNS Server</LogName>

      <Expression>

        <And>

          <Expression>

            <RegExExpression>

              <ValueExpression>

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

              </ValueExpression>

              <Operator>MatchesMOM2005RegularExpression</Operator>

              <Pattern>^(1540|1541|1542|1543|1544|1545|1546|1547)$</Pattern>

            </RegExExpression>

          </Expression>

          <Expression>

            <SimpleExpression>

              <ValueExpression>

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

              </ValueExpression>

              <Operator>Equal</Operator>

              <ValueExpression>

                <Value>DNS</Value>

              </ValueExpression>

            </SimpleExpression>

          </Expression>

        </And>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

    <WriteAction ID="GenerateAlert" TypeID="MomBackwardCompatibility!System.Mom.BackwardCompatibility.AlertResponse">

      <AlertGeneration>

        <GenerateAlert>true</GenerateAlert>

        <Owner/>

        <Description>

            $Data/EventDescription$

          </Description>

        <AlertLevel>40</AlertLevel>

        <ResolutionState/>

        <Source>

            $Data/PublisherName$

          </Source>

        <Name>Core Service Domain Name Problems</Name>

      </AlertGeneration>

      <InvokerType>0</InvokerType>

    </WriteAction>

    <WriteAction ID="CollectEventData" TypeID="SystemCenterLibrary!Microsoft.SystemCenter.CollectEvent"/>

    <WriteAction ID="CollectEventDataWarehouse" TypeID="DataWarehouseLibrary!Microsoft.SystemCenter.DataWarehouse.PublishEventData"/>

  </WriteActions>

</Rule>