DNS event messages 1 through 1614 in Windows Server 2003

This article describes DNS server events that may be displayed in the event logs on a Microsoft Windows Server 2003-based DNS server. This article describes event ID 1 through event ID 1614.

Informational

1

MessageId=1
Severity=Informational
SymbolicName=DNS_EVENT_STARTING

Starting Microsoft DNS Server

2

MessageId=2
Severity=Informational
SymbolicName=DNS_EVENT_STARTUP_OK

The DNS server has started.

3

MessageId=3
Severity=Informational
SymbolicName=DNS_EVENT_SHUTDOWN

The DNS server has shutdown.

Initialization

111

MessageId=111
Severity=Error
SymbolicName=DNS_EVENT_CANNOT_CREATE_THREAD

The DNS server could not create a thread. The system may be out of resources. You might close programs not in use, restart the DNS server or reboot your computer. The event data is the error code.

112

MessageId=112
Severity=Error
SymbolicName=DNS_EVENT_RECURSION_INIT_FAILED

The DNS server could not initialize a recursion thread. The system may be out of resources. You might close programs not in use, restart the DNS server or reboot your computer. The event data is the error code.

113

MessageId=113
Severity=Informational
SymbolicName=DNS_EVENT_SERVICE_NOTIFY

The DNS server could not signal the service "%1". The error was %2. There may be interoperability problems between the DNS service and this service.

WINS + NBSTAT

130

MessageId=130
Severity=Error
SymbolicName=DNS_EVENT_WINS_INIT_FAILED

The DNS server could not initialize WINS lookup. The system may be out of resources. You might close programs not in use, restart the DNS server or reboot your computer. The event data is the error code.

131

MessageId=131
Severity=Error
SymbolicName=DNS_EVENT_NBSTAT_INIT_FAILED

The DNS server did not initialize WINSR reverse lookup, through NetBIOS adapter status lookup. The server will continue to run but will not attempt to perform WINS reverse lookups. This may be due to an incorrect configuration. If WINSR lookup is not required, remove WINSR records from zone data files and reload modified zones or restart the DNS server. If the DNS server should support WINSR reverse lookup, restart the server computer and verify that the WINS/NetBT configuration for TCP/IP client properties on the computer are correctly set.

132

MessageId=132
Severity=Warning
SymbolicName=DNS_EVENT_NBSTAT_ADAPTER_FAILED

The DNS server did not open adapter %1, for NETBIOS adapter status lookup.

RPC initialization

140

MessageId=140
Severity=Error
SymbolicName=DNS_EVENT_RPC_SERVER_INIT_FAILED

The DNS server could not initialize the remote procedure call (RPC) service. If it is not running, start the RPC service or reboot the computer. The event data is the error code.

Winsock/Interface Initialization

403

MessageId=403
Severity=Error
SymbolicName=DNS_EVENT_CANNOT_CREATE_TCP_SOCKET

The DNS server could not create a Transmission Control Protocol (TCP) socket. Restart the DNS server or reboot the computer. The event data is the error code.

404

MessageId=404
Severity=Error
SymbolicName=DNS_EVENT_CANNOT_BIND_TCP_SOCKET

The DNS server could not bind a Transmission Control Protocol (TCP) socket to address %1. The event data is the error code. An IP address of 0.0.0.0 can indicate a valid "any address" configuration in which all configured IP addresses on the computer are available for use. Restart the DNS server or reboot the computer.

405

MessageId=405
Severity=Error
SymbolicName=DNS_EVENT_CANNOT_LISTEN_TCP_SOCKET

The DNS server could not listen on Transmission Control Protocol (TCP) socket for address %1. The event data is the error code. An IP address of 0.0.0.0 can indicate a valid "any address" configuration in which all configured IP addresses on the computer are available for use. Restart the DNS server or reboot the computer.

406

MessageId=406
Severity=Error
SymbolicName=DNS_EVENT_CANNOT_CREATE_UDP_SOCKET

The DNS server could not create a User Datagram Protocol (UDP) socket. The event data is the error code. Restart the DNS server or reboot your computer.

407

MessageId=407
Severity=Error
SymbolicName=DNS_EVENT_CANNOT_BIND_UDP_SOCKET

The DNS server could not bind a User Datagram Protocol (UDP) socket to %1. The event data is the error code. Restart the DNS server or reboot your computer.

408

MessageId=408
Severity=Error
SymbolicName=DNS_EVENT_OPEN_SOCKET_FOR_ADDRESS

The DNS server could not open socket for address %1. Verify that this is a valid IP address for the server computer. If it is not valid use the Interfaces dialog under Server Properties in the DNS Manager to remove it from the list of IP interfaces. Then stop and restart the DNS server. (If this was the only IP interface on this computer and the DNS server may not have started as a result of this error. In that case remove the DNS\Parameters\ListenAddress value in the services section of the registry and restart.) If this is a valid IP address for this computer, make sure that no other program (e.g. another DNS server) is running that would attempt to use the DNS port. For more information, see "DNS server log reference" in the online Help.

409

MessageId=409
Severity=Warning
SymbolicName=DNS_EVENT_UPDATE_LISTEN_ADDRESSES

The DNS server list of restricted interfaces contains IP addresses that are not configured for use at the server computer. Use the DNS manager server properties, interfaces dialog, to verify and reset the IP addresses the DNS server should listen on. For more information, see "To restrict a DNS server to listen only on selected addresses" in the online Help.

410

MessageId=410
Severity=Error
SymbolicName=DNS_EVENT_INVALID_LISTEN_ADDRESSES

The DNS server list of restricted interfaces does not contain a valid IP address for the server computer. The DNS server will use all IP interfaces on the computer. Use the DNS manager server properties, interfaces dialog, to verify and reset the IP addresses the DNS server should listen on. For more information, see "To restrict a DNS server to listen only on selected addresses" in the online Help.

411

MessageId=411
Severity=Error
SymbolicName=DNS_EVENT_HOSTENT_MAX_IPS

The DNS server did not bind to all IP addresses available on this server. Please use the DnsManger server properties interfaces tab to edit the list of IP addresses on which DNS is running. Add any missing IP addresses to the list. After adding any additional IP addresses to the interfaces list, you MUST stop and restart the DNS service for the new interfaces to receive DNS service. For more information, see "To restrict a DNS server to listen only on selected addresses" in the online Help. Note that each additional IP interface does consume system resources and adds a small performance overhead to query reception. There is no benefit in DNS to additional addresses beyond those necessary to support the available network cards. Even if the DNS server is handling multiple zones registered with the Internic, it is not necessary to have different IPs registered for each zone. Hence, although the individual effect is small, since a very large number of IP interfaces may degrade performance, you are encouraged to remove from the computer any IP addresses that are unnecessary.

412

MessageId=412
Severity=Warning
SymbolicName=DNS_EVENT_MANY_IP_INTERFACES

The DNS server is bound to a large number of IP addresses. Each of these server IP addresses consumes additional system resources and can add a slight increase in performance overhead for DNS query reception. In most cases, you can remove secondary IP addresses that are not required to support server networking hardware. For more information, see "Configuring multihomed servers" in the online Help.

413

MessageId=413
Severity=Warning
SymbolicName=DNS_EVENT_NON_DNS_PORT

The DNS server will send requests to other DNS servers on a port other than its default port (TCP port 53). This is done to accommodate configuration changes you have made at the DNS server and prevent it from failing to receive DNS queries it makes to other servers. You might want to change this behavior. For more information, see "DNS server log reference" in the online Help.

This DNS server is multi-homed (running on multiple IP addresses), but has been configured not to run on ALL IP addresses available on the computer. Under these conditions it is impossible to guarantee that a DNS query to a remote DNS server will be sent with one the IP addresses the DNS server is using, and hence, whether the response to that IP address, will be received on the DNS port. To avoid this problem, sends to other DNS servers will be done on a arbitrary (non-DNS) port, and the response will be received regardless of the IP address used.

If you want to use the DNS port for sends to other DNS servers, then you must change your configuration to either:

Use all IP addresses on the computer for DNS (eliminate the listen address list)

-or-

Limit the DNS server to use a single IP address

414

MessageId=414
Severity=Warning
SymbolicName=DNS_EVENT_SINGLE_LABEL_HOSTNAME

The DNS server computer currently has no DNS domain name. Its DNS name is a single label hostname with no domain (example: "host" rather than "host.microsoft.com").

You might have forgotten to configure a primary DNS domain for the server computer. For more information, see either "DNS server log reference" or "To configure the primary DNS suffix for a client computer" in the online Help.

While the DNS server has only a single label name, all zones created will have default records (SOA and NS) created using only this single label name for the server's hostname. This can lead to incorrect and failed referrals when clients and other DNS servers use these records to locate this server by name.

To correct this problem:

1. Open Control Panel.
2. Start the System tool.
3. Click the Network Identification tab.
4. Click Properties.
5. Type a domain name or work group name. This is used as your DNS domain name.
6. Reboot the computer to initialize with new domain name.

After the reboot, the DNS server will attempt to fix up default records, substituting new DNS name of this server, for old single label name. However, you should review to make sure zone's SOA and NS records now properly use correct domain name of this server.

Registry Boot Problems

500

MessageId=500
Severity=Error
SymbolicName=DNS_EVENT_INVALID_REGISTRY_ZONE

The DNS server has detected that the zone %1 has invalid or corrupted registry data. To correct the problem, you can delete the applicable zone subkey, located under DNS server parameters in the Windows 2000 registry. You can then recreate the zone using the DNS console. For more information, see "Tuning advanced server parameters" and "Add and Remove Zones" in the online Help.

501

MessageId=501
Severity=Error
SymbolicName=DNS_EVENT_INVALID_ZONE_TYPE

The DNS server has detected that the zone %1 has a missing or corrupted zone type in registry data. To correct the problem, you can delete the applicable zone subkey, located under DNS server parameters in the windows 2000 registry. You can then recreate the zone using the DNS console. For more information, see "Tuning advanced server parameters" and "Add and Remove Zones" in the online Help.

502

MessageId=502
Severity=Error
SymbolicName=DNS_EVENT_NO_ZONE_FILE

The DNS server has detected that for the primary zone %1 its has no zone file name stored in registry data. You can either update the zone file name or delete the zone and recreate it using the DNS console. To delete the applicable zone from the registry, locate its subkey under DNS server parameters in the Windows 2000 registry. You can then recreate the zone using the DNS console. For more information, see "To change a zone file name", "Tuning advanced server parameters" and "Add and Remove Zones" in the online Help.

503

MessageId=503
Severity=Error
SymbolicName=DNS_EVENT_SECONDARY_REQUIRES_MASTERS

The DNS server has detected that the secondary zone %1 has no master IP addresses in registry data. Secondary zones require at least one master server to act as a source. You can add or update the IP address for the master server for this zone using the DNS console. For more information, see "To update the master server for a secondary zone" in the online Help.

504

MessageId=504
Severity=Error
SymbolicName=DNS_EVENT_REG_ZONE_CREATION_FAILED

The DNS server could not create zone %1 from registry data. One or more of the zone registry key values could be corrupted or the zone file is missing. Use the DNS console to replace or repair any corrupted registry key values or confirm that the zone database is available. For more information, see "Configure zone properties" in the online Help.

505

MessageId=505
Severity=Error
SymbolicName=DNS_EVENT_INVALID_REGISTRY_ZONE_DATA

The DNS server zone %1 has invalid or corrupted registry data for %2. Use the DNS console to replace or repair any corrupted registry key values or confirm that the zone database is available. For more information, see the online Help.

506

MessageId=506
Severity=Error
SymbolicName=DNS_EVENT_INVALID_REGISTRY_PARAM

The DNS server has invalid or corrupted registry parameter %1. To correct the problem, you can delete the applicable registry value, located under DNS server parameters in the Windows 2000 registry. You can then recreate it using the DNS console. For more information, see the online Help.

507

MessageId=507
Severity=Error
SymbolicName=DNS_EVENT_INVALID_REGISTRY_FORWARDERS

The DNS server encountered invalid or corrupted forwarder parameters in registry data.

To fix the forwarders:

1. Connect to or open this server in DNS Manager.
2. Open Server properties.
3. Click the Forwarders tab.
4. Reset the forwarder information to the appropriate values.
5. Click OK.

For more information, see the online Help.

General Database Load Events

706

MessageId=706
Severity=Warning
SymbolicName=DNS_EVENT_NO_ROOT_NAME_SERVER

The DNS server does not have a cache or other database entry for root name servers. Either the root hints file, Cache.dns, or Active Directory must have at least one name server (NS) resource record, indicating a root DNS server and a corresponding host (A) resource record for that root DNS server. Otherwise, the DNS server will be unable to contact the root DNS server on startup and will be unable to answer queries for names outside of its own authoritative zones. To correct this problem, use the DNS console to update the server root hints. For more information, see the online Help.

707

MessageId=707
Severity=Error
SymbolicName=DNS_EVENT_NO_CACHE_FILE_SPECIFIED

The DNS server is not root authoritative and no root hints were specified in the Cache.dns file. Where the server is not a root server, this file must specify root hints in the form of at least one name server (NS) resource record, indicating a root DNS server and a corresponding host (A) resource record for that root DNS server. Otherwise, the DNS server will be unable to contact the root DNS server on startup and will be unable to answer queries for names outside of its own authoritative zones. To correct this problem, use the DNS console to update the server root hints. For more information, see the online Help.

708

MessageId=708
Severity=Informational
SymbolicName=DNS_EVENT_CACHING_SERVER_ONLY

The DNS server did not detect any zones of either primary or secondary type. It will run as a caching-only server but will not be authoritative for any zones. For more information, see the online Help.

709

MessageId=709
Severity=Informational
SymbolicName=DNS_EVENT_MOVE_ROOT_HINTS_TO_DOMAIN_DP

The DNS server has moved the AD-integrated root hint data for all DNS servers in this domain to the %1 directory partition.

710

MessageId=710
Severity=Informational
SymbolicName=DNS_EVENT_ZONE_RESET_TYPE_COMPLETE_FILE

An administrator has changed the type and zone storage options of zone %1.The zone is now type %2. The zone will be stored in the zone file %3.

711

MessageId=711
Severity=Informational
SymbolicName=DNS_EVENT_ZONE_RESET_TYPE_COMPLETE_DS

An administrator has changed the type and/or Active Directory location of zone %1.The zone is now type %2. The zone will be stored in Active Directory at %3.

712

MessageId=712
Severity=Informational
SymbolicName=DNS_EVENT_ZONE_MOVE_COMPLETE_FILE

An administrator has changed the zone storage options for zone %1. The zone will now be stored in the zone file %2.

713

MessageId=713
Severity=Informational
SymbolicName=DNS_EVENT_ZONE_MOVE_COMPLETE_DS

An administrator has moved the zone %1 to a new location in Active Diretory. The zone will be stored in Active Directory at %2.

Sanity Check Problems

132

MessageId=800
Severity=Informational
SymbolicName=DNS_EVENT_ZONE_BAD_PRIMARY_SERVER

The zone %1 is configured to accept updates but the A record for the primary server in the zone's SOA record is not available on this DNS server. This may indicate a configuration problem. If the address of the primary server for the zone cannot be resolved DNS clients will be unable to locate a server to accept updates for this zone. This will cause DNS clients to be unable to perform DNS updates.

File Loading Problems

1000

MessageId=1000
Severity=Error
SymbolicName=DNS_EVENT_FILE_OPEN_ERROR

The DNS server could not open the file %1. Check that the file exists in the %SystemRoot%\System32\Dns folder and that it contains valid data. The event data is the error code.

1001

MessageId=1001
Severity=Error
SymbolicName=DNS_EVENT_FILE_NOT_MAPPED

The DNS server could not map file %1 to memory. Either close other programs that are not in use or reboot the computer to reclaim additional memory for the server to use.

1003

MessageId=1003
Severity=Error
SymbolicName=DNS_EVENT_CACHE_FILE_NOT_FOUND

The DNS server could not find or open the root hints file, Cache.dns, in the %SystemRoot%\System32\Dns folder. Verify that this file is located in this folder and that it contains at least one name server (NS) resource record, indicating a root DNS server and a corresponding host (A) resource record for that server. For more information, see the online Help.

1004

MessageId=1004
Severity=Error
SymbolicName=DNS_EVENT_COULD_NOT_OPEN_DATABASE

The DNS server could not find or open zone file %1. in the %SystemRoot%\System32\Dns folder. Verify that the zone file is located in this folder and that it contains valid data.

1008

MessageId=1008
Severity=Error
SymbolicName=DNS_EVENT_FILE_PATH_TOO_LONG

The DNS server was unable to create the path for file %1 in folder %2. The specified path is too long. Choose a different path.

Boot File Problems

1200

MessageId=1200
Severity=Error
SymbolicName=DNS_EVENT_BOOT_FILE_NOT_FOUND

The DNS server could not find or open boot file %1. This file should be called 'Boot' and be located in the %SystemRoot%\System32\Dns folder.

1201

MessageId=1201
Severity=Error
SymbolicName=DNS_EVENT_ZONE_CREATION_FAILED

The DNS server could not create zone %1 specified in file %2 at line %3. Check that the zone file is located in the SystemRoot%\System32\Dns folder and that it contains valid data.

1202

MessageId=1202
Severity=Warning
SymbolicName=DNS_EVENT_DIRECTORY_DIRECTIVE

The DNS server encountered an unsupported 'folder' directive in the server boot file %1 at line %2. All database files must be located in the "%SystemRoot%\system32\dns" folder. The folder directive is ignored.

1203

MessageId=1203
Severity=Error
SymbolicName=DNS_EVENT_NO_FORWARDING_ADDRESSES

The DNS server encountered a 'forwarders' directive in with no forwarding addresses in file %1 at line %2. Although the DNS server will continue running it will not be able to forward unresolved queries to the forwarders. To correct the problem, in the DNS console select the server in the console tree, then from the Action menu, click Properties and click the Forwarders tab. Add IP addresses for forwarders. For more information, see "Using forwarders" in the online Help.

1204

MessageId=1204
Severity=Error
SymbolicName=DNS_EVENT_SLAVE_REQUIRES_FORWARDERS

The DNS server encountered a 'slave' directive without a preceding forwarders list in file %1 at line %2. Although the server will continue to run it will not be able to forward unresolved queries to the forwarders. To correct the problem, in the DNS console select the server in the console tree, then from the Action menu, click Properties and click the Forwarders tab. Add IP addresses for forwarders. For more information, see "Using forwarders" in the online Help.

1205

MessageId=1205
Severity=Error
SymbolicName=DNS_EVENT_UNKNOWN_BOOTFILE_OPTION

The DNS server encountered an unknown boot option %1 in file %2 at line %3. The option is ignored. You may want to remove it the option from the boot file which is located in the %SystemRoot%\System32\Dns folder.

1206

MessageId=1206
Severity=Error
SymbolicName=DNS_EVENT_MISSING_DIRECTORY_NAME DNS

Server encountered missing database folder name, in file %1, line %2.

Database File Parsing Problems

1501

MessageId=1501
Severity=Error
SymbolicName=DNS_EVENT_COULD_NOT_PARSE_DATABASE

The DNS server could not parse zone file %1 for zone %2. Check that the zone file is located in the %SystemRoot%\System32\Dns folder and that it contains valid data.

1502

MessageId=1502
Severity=Error
SymbolicName=DNS_EVENT_DATABASE_PARSING_ERROR

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

1503

MessageId=1503
Severity=Error
SymbolicName=DNS_EVENT_PARSING_ERROR_LINE

The DNS server could not parse the zone file %1 at line %2. Although the DNS server continues to load, ignoring this line, it is recommended that you either correct the line or remove it from the zone file. The zone file is located in the %SystemRoot%\System32\Dns folder.

1504

MessageId=1504
Severity=Error
SymbolicName=DNS_EVENT_UNEXPECTED_TOKEN

The DNS server could not parse an unexpected 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, which is located in the %SystemRoot%\System32\Dns folder.

1505

MessageId=1505
Severity=Error
SymbolicName=DNS_EVENT_UNEXPECTED_END_OF_TOKENS

The DNS server unexpected end of line, in zone file %1 at line %2. To correct the problem, fix this line in the zone file, which is located in the %SystemRoot%\System32\Dns folder.

1506

MessageId=1506
Severity=Error
SymbolicName=DNS_EVENT_INVALID_TOKEN

The DNS server encountered 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 this resource record from the zone file. The zone file is located in the %SystemRoot%\System32\Dns folder.

1507

MessageId=1507
Severity=Error
SymbolicName=DNS_EVENT_INVALID_CLASS_TOKEN

The DNS server encountered invalid class token "%1" in zone file %2 at line %3. Although the DNS server continues to load, ignoring this resource record (RR), it is recommended that you either correct the class of the RR to use the Internet (IN) class or remove the resource record from the zone file. The DNS server supports only the Internet (IN) class in RRs.

1508

MessageId=1508
Severity=Error
SymbolicName=DNS_EVENT_IGNORING_FILE_RECORD

The DNS server is ignoring an invalid resource record in zone file %1 at line %2. See the previously logged event for a description of the error. Although the DNS server continues to load, ignoring this RR, it is recommended that you investigate the error associated with this record and either correct it or remove it from the zone file.

Directive Problems

1520

MessageId=1520
Severity=Warning
SymbolicName=DNS_EVENT_UNKNOWN_DIRECTIVE

The DNS server encountered the unknown directive '%1' in file %2 at line %3. The directive was ignored.

1521

MessageId=1521
Severity=Warning
SymbolicName=DNS_EVENT_UNSUPPORTED_DIRECTIVE

The DNS server encountered the unsupported directive '%1' in file %2 at line %3. The directive was ignored.

1522

MessageId=1522
Severity=Warning
SymbolicName=DNS_EVENT_OBSOLETE_DIRECTIVE

The DNS server encountered the obsolete directive '%1' in file %2 at line %3. The directive was ignored.

1523

MessageId=1523
Severity=Warning
SymbolicName=DNS_EVENT_DIRECTIVE_NOT_YET_IMPLEMENTED

The DNS server encountered the directive '%1' in file %2 at line %3. The directive is not yet supported and was ignored.

Domain Name Problems

1540

MessageId=1540
Severity=Error
SymbolicName=DNS_EVENT_DOMAIN_NODE_CREATION_ERROR

The DNS server unable to create domain node.

1541

MessageId=1541
Severity=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

MessageId=1542
Severity=Error
SymbolicName=DNS_EVENT_INVALID_DOTTED_DOMAIN_NAME

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

1543

MessageId=1543
Severity=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

MessageId=1544
Severity=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

MessageId=1545
Severity=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

MessageId=1546
Severity=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

MessageId=1547
Severity=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.

Resource Record Problems

1600

MessageId=1600
Severity=Error
SymbolicName=DNS_EVENT_UNKNOWN_RESOURCE_RECORD_TYPE

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

1601

MessageId=1601
Severity=Warning
SymbolicName=DNS_EVENT_OBSOLETE_RECORD_SKIPPED DNS

Server encountered the obsolete record type %1 in database file %2, line %3. The record was ignored.

MD or MF record types are obsolete. They should be converted to a MX record type which has the format: MX

For example:

For more information, see the "Resource records reference" topic in the online Help.

1602

MessageId=1602
Severity=Error
SymbolicName=DNS_EVENT_INVALID_SOA_RECORD The DNS server encountered an invalid SOA (Start Of Authority) resource record (RR) in file %1 at line %2. An SOA record is required in every zone files and must satisfy the following conditions:

• The SOA record must be the first record in the zone file.
• The SOA record must belong to the root of the zone ("@" in zone file).
• Only one SOA is allowed in the zone.
• SOA records are not valid in the root-hints (Cache.dns) file.

To correct the problem modify or repair the SOA RR in zone file %1, which can be found in the %SystemRoot%\System32\Dns folder. For more information, see the "Resource records reference" in the online Help.

1610

MessageId=1610
Severity=Error
SymbolicName=DNS_EVENT_PARSED_ADD_RR_AT_CNAME

The DNS server encountered a resource record (RR) in the zone file %1 at line %2 for a domain name with an existing CNAME (alias) RR. Where used, CNAME RRs must be the only RR for the domain name they are used to provide an alias for. Either this RR, or the CNAME RR it conflicts with, needs to be deleted from zone file %1, which can be found in the %SystemRoot%\System32\Dns folder.

1611

MessageId=1611
Severity=Error
SymbolicName=DNS_EVENT_PARSED_CNAME_NOT_ALONE

The DNS server encountered a CNAME (alias) resource record (RR) in zone file %1 at line %2 for a domain name with existing RRs. Where used, CNAME RRs must be the only RR for the domain name they are used to provide an alias for. Either this CNAME RR, or the one it conflicts with, needs to be deleted from zone file %1, which can be found in the %SystemRoot%\System32\Dns folder.

1612

MessageId=1612
Severity=Error
SymbolicName=DNS_EVENT_PARSED_CNAME_LOOP

The DNS server encountered an CNAME (alias) resource record (RR) in zone file %1 at line %2 that forms an CNAME loop with another CNAME RR in the zone. One of the CNAME RRs forming the loop must be removed from the zone file. The zone file is located in the %SystemRoot%\System32\Dns folder.

1613

MessageId=1613
Severity=Error
SymbolicName=DNS_EVENT_INVALID_PREFERENCE

The DNS server encountered an invalid preference value "%1" in zone file %2 at line %3. The preference must be a valid 16-bit unsigned integer. To correct the problem, modify the preference field to a valid value. The zone file %2 is located in the %SystemRoot%\System32\Dns folder.

1614

MessageId=1614
Severity=Error
SymbolicName=DNS_EVENT_INVALID_DWORD_TOKEN

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

For additional information about Windows Server 2003 DNS event messages 1616 through 6702, click the following article number to view the article in the Microsoft Knowledge Base: