Home
  •  

Microsoft Windows Server DNS Configuration SingleLabelHostname

Microsoft.Windows.Server.DNS.Configuration.SingleLabelHostname (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 machine currently has no DNS domain name. Its DNS name is a single label hostname with no domain.

Resolutions

Give the DNS server a fully qualified domain name

The DNS server must be configured with a fully qualified domain name (FQDN) to function properly. This computer is configured with a single-label name.

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

To give the DNS server an FQDN:

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

2.Click Change system properties.

3.On the Computer Name tab, click Change.

4.In Computer Name/Domain Changes, click More.

5.In Primary DNS Suffix of this computer, type the primary Domain Name System (DNS) suffix of the computer (the part of the computer's FQDN that follows the host name), and then click OK.

6.Click OK, and then click Close to close all the dialog boxes.

7.Restart the computer to allow the changes to take effect. To restart the computer, click Start, click the arrow next to the Lock button, and then click Restart.

After the computer restarts, the DNS server attempts to fix default records, substituting the new DNS name of this server for the single-label name. However, ensure that each zone's start of authority (SOA) and name server (NS) resource records now use the correct domain name of this server.

To view the start of authority (SOA) and name server (NS) resource records:

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, expand Roles, expand DNS Server, and then expand DNS.

3.For each zone, expand the zone folder that contains the zone, expand the zone, and then click Properties.

4.To view the start of authority (SOA) resource records, click the Start of Authority (SOA) tab.

5.To view the name server (NS) resource records, click the Name Servers tab.

Instead of directly specifying the primary DNS suffix, you can join the computer to a Windows domain. The DNS name of the Windows domain is then used as the primary DNS suffix of the server's name.

External

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

Element properties:

TargetMicrosoft.Windows.Server.DNS.Server
CategoryAlert
EnabledTrue
Alert GenerateTrue
Alert SeverityWarning
Alert PriorityNormal
RemotableTrue
Alert Message
Windows DNS - Configuration - Single Label Hostname

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.SingleLabelHostname" 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">414</Value>

          </ValueExpression>

        </SimpleExpression>

      </Expression>

    </DataSource>

  </DataSources>

  <WriteActions>

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

      <Priority>1</Priority>

      <Severity>1</Severity>

      <AlertOwner/>

      <AlertMessageId>$MPElement[Name="Microsoft.Windows.Server.DNS.Configuration.SingleLabelHostname.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>