Export (0) Print
Expand All

DNS Server Configuration

Updated: November 13, 2007

Applies To: Windows Server 2008

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.

 

Events

Event ID Source Message

150

Microsoft-Windows-DNS-Server-Service

The DNS server could not load or initialize the plug-in DLL %1. The event data is the error code returned by the plug-in DLL load or initialization attempt. Please correct the plug-in error that is causing this condition or remove the plug-in from the DNS server configuration.

408

Microsoft-Windows-DNS-Server-Service

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 machine 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 machine, make sure that no other application (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

Microsoft-Windows-DNS-Server-Service

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

Microsoft-Windows-DNS-Server-Service

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 machine.

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.

414

Microsoft-Windows-DNS-Server-Service

The DNS server machine 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) open System applet
3) select Computer Name tab
4) click the "Change" button and join the computer to a domain or workgroup; this name will be used as your DNS domain name
5) reboot to initialize with new domain name

After 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.

500

Microsoft-Windows-DNS-Server-Service

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 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

Microsoft-Windows-DNS-Server-Service

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 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

Microsoft-Windows-DNS-Server-Service

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 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

Microsoft-Windows-DNS-Server-Service

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

Microsoft-Windows-DNS-Server-Service

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

Microsoft-Windows-DNS-Server-Service

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

Microsoft-Windows-DNS-Server-Service

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 registry. You can then recreate it using the DNS console. For more information, see the online Help.

507

Microsoft-Windows-DNS-Server-Service

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

To fix the forwarders:
%t - connect to or open this server in DNS Manager
%t - bring up server properties
%t - open "Forwarders" tab
%t - reset forwarders information to desired values
%t - click OK

For more information, see the online Help.

800

Microsoft-Windows-DNS-Server-Service

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.

1000

Microsoft-Windows-DNS-Server-Service

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

1004

Microsoft-Windows-DNS-Server-Service

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

1200

Microsoft-Windows-DNS-Server-Service

The DNS server could not find or open the boot file %1. This file must be called Boot, and it must be located in the %SystemRoot%\System32\Dns directory.

1201

Microsoft-Windows-DNS-Server-Service

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 directory and that it contains valid data.

1202

Microsoft-Windows-DNS-Server-Service

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

1203

Microsoft-Windows-DNS-Server-Service

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.

1205

Microsoft-Windows-DNS-Server-Service

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 directory.

1206

Microsoft-Windows-DNS-Server-Service

DNS server encountered missing database directory name, in file %1, line %2.

1501

Microsoft-Windows-DNS-Server-Service

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

1502

Microsoft-Windows-DNS-Server-Service

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 directory.

1503

Microsoft-Windows-DNS-Server-Service

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 directory.

1504

Microsoft-Windows-DNS-Server-Service

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 directory.

1505

Microsoft-Windows-DNS-Server-Service

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 directory.

1506

Microsoft-Windows-DNS-Server-Service

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 directory.

1507

Microsoft-Windows-DNS-Server-Service

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

Microsoft-Windows-DNS-Server-Service

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.

1520

Microsoft-Windows-DNS-Server-Service

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

1521

Microsoft-Windows-DNS-Server-Service

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

1522

Microsoft-Windows-DNS-Server-Service

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

1523

Microsoft-Windows-DNS-Server-Service

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

1540

Microsoft-Windows-DNS-Server-Service

The DNS server was unable to create a domain node.

1541

Microsoft-Windows-DNS-Server-Service

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 directory.

1542

Microsoft-Windows-DNS-Server-Service

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

1543

Microsoft-Windows-DNS-Server-Service

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 directory.

1544

Microsoft-Windows-DNS-Server-Service

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 directory.

1545

Microsoft-Windows-DNS-Server-Service

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 directory.

1546

Microsoft-Windows-DNS-Server-Service

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 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 directory. For more information, see "Delegating zones" in the online Help.

1547

Microsoft-Windows-DNS-Server-Service

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 directory. For more information, see "Delegating zones" in the online Help.

1600

Microsoft-Windows-DNS-Server-Service

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 directory.

1601

Microsoft-Windows-DNS-Server-Service

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 MX record type which has the format: MX <preference value> <mail server domain name>
Example:
%tmicrosoft.com MX 10 mai1.microsoft.com.

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

1602

Microsoft-Windows-DNS-Server-Service

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 satify the following conditions:
1) The SOA record must be the first record in the zone file.
2) The SOA record must belong to the root of the zone ("@" in zone file).
3) Only one SOA is allowed in the zone.
4) SOA records are NOT valid in 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 directory. For more information, see the "Resource records reference" in the online Help.

1610

Microsoft-Windows-DNS-Server-Service

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 directory.

1611

Microsoft-Windows-DNS-Server-Service

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 directory.

1612

Microsoft-Windows-DNS-Server-Service

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

1613

Microsoft-Windows-DNS-Server-Service

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 directory.

1614

Microsoft-Windows-DNS-Server-Service

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 directory.

1616

Microsoft-Windows-DNS-Server-Service

The DNS server encountered a text string "%1" in zone file %2 at line %3 that exceeds the maximum permissible length. Although the DNS server continues to load, ignoring this resource record (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 directory.

1617

Microsoft-Windows-DNS-Server-Service

The DNS server encountered an invalid IP address "%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 this RR or remove it from the zone file. The zone file is located in the %SystemRoot%\System32\Dns directory.

1618

Microsoft-Windows-DNS-Server-Service

The DNS server encountered an invalid IPv6 address "%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 this RR or remove it from the zone file. The zone file is located in the %SystemRoot%\System32\Dns directory.

1619

Microsoft-Windows-DNS-Server-Service

The DNS server could not find protocol "%1" specified for the well known service (WKS) resource record (RR) in zone file %2 at line %3. Although the DNS server continues to load, ignoring this RR, it is strongly recommended that you either correct this WKS RR or remove it from the zone file. The zone file is located in the %SystemRoot%\System32\Dns directory.

1620

Microsoft-Windows-DNS-Server-Service

The DNS server could not find the service "%1" specified for the well known service (WKS) resource record (RR) in zone file %2 at line %3. Although the DNS server continues to load, ignoring this RR, it is recommended that you either correct this WKS RR or remove it from the zone file. The zone file is located in the %SystemRoot%\System32\Dns directory.

1621

Microsoft-Windows-DNS-Server-Service

The DNS server encountered the port "%1" specified for the well known service (WKS) resource record (RR) in zone file %2 at line %3. This port exceeds the maximum port supported for the WKS RR. Although the DNS server continues to load, ignoring this RR, it is strongly recommended that you either correct this WKS RR or remove it from the zone file. The zone file is located in the %SystemRoot%\System32\Dns directory.

1650

Microsoft-Windows-DNS-Server-Service

The DNS server encountered invalid WINS record in file %1, line %2.

WINS records are subject to the following conditions:
1) WINS record must be in forward lookup zone (not in in-addr.arpa domain).
2) Only one WINS record may be specified in a zone file.
3) WINS record must belong to the zone root (the WINS record name must be the origin of the zone). If WINS lookup is desired for names in a sub-domain of the zone, then the sub-domain must be split into its own zone.
4) WINS record must specify at least one WINS server.

The format of a WINS record:
WINS [LOCAL] [L<lookup timeout>] [C<cache timeout>] <WINS IP> [WINS IPs...]

Examples (zone root assumed to be current origin):
@ IN WINS LOCAL L1 C10 10.10.10.1 10.10.10.2 10.10.10.3
@ IN WINS 10.10.10.1

For more information, see "Using WINS lookup" in the online Help.

1651

Microsoft-Windows-DNS-Server-Service

The DNS server encountered an invalid WINS reverse lookup (WINSR) resource record (RR) in file %1 at line %2.

WINSR records are subject to the following conditions:
1) WINSR record must be in reverse lookup zone (under in-addr.arpa domain).
2) Only one WINSR record may be specified in a zone file.
3) WINSR record must belong to the zone root (the WINS record name must be the origin of the zone).
4) WINSR record must specify at domain for the resulting name.

The format of a WINSR record:
WINSR [LOCAL] [L<lookup timeout>] [C<cache timeout>] <result domain>

Examples (zone root assumed to be current origin):
@ IN WINSR LOCAL L1 C10 microsoft.com.
@ IN WINSR wins.microsoft.com.

For more information, see "Using WINS lookup" in the online Help.

1654

Microsoft-Windows-DNS-Server-Service

The DNS server encountered an unknown WINS-to-DNS mapping flag %1 in file %2 at line %3. Although the DNS server continues to load, ignoring this flag, it is recommended that you either correct the associated resource record or remove it from the zone file. The zone file is located in the %SystemRoot%\System32\Dns directory.

1656

Microsoft-Windows-DNS-Server-Service

The DNS server encountered a WINS reverse lookup (WINSR) resource record (RR) without a domain specified for resulting names in zone file %1 at line %2. This field is required for mapping names that are found in WINS reverse lookup to fully-qualfied DNS domain names. It is appended to the NetBIOS computer names resolved by NetBIOS adapter status queries. Although the DNS server will continue to load, ignoring this RR, it is recommended that you either correct the WINSR RR or disable WINS reverse lookup and/or remove the RR from the zone file. The zone file is located in the %SystemRoot%\System32\Dns directory. For more information, see "Using WINS lookup" in the online Help.

2003

Microsoft-Windows-DNS-Server-Service

The DNS server encountered an error writing current configuration back to boot file. Verify that the current boot file contains all of the desired information. The Boot file is located in the %SystemRoot%\System32\Dns directory.

2200

Microsoft-Windows-DNS-Server-Service

The DNS server could not open a registry key. Reinstall the DNS server if it was not able to be started. If the DNS server started, but couldn't load a zone, reload the zone or restart the DNS server.

2202

Microsoft-Windows-DNS-Server-Service

The DNS server could not write a registry key. The server disk could be full or corrupted or the maximum permissible size for the server registry has been reached. The DNS server will not be able to save server or zone configuration parameters to in the registry unless the problem is fixed.

2203

Microsoft-Windows-DNS-Server-Service

The DNS server could not delete a registry key. The registry is likely corrupted. The DNS server will not be able to save DNS server or zone configuration parameters in the registry unless the problem is fixed.

2204

Microsoft-Windows-DNS-Server-Service

The registry value HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters\%1 contains an invalid value or could not be read. The DNS server cannot start. You must change this value to valid data or delete it and then attempt to restart the DNS service.

3160

Microsoft-Windows-DNS-Server-Service

The DNS server encountered an non-writeable or unknown resource record (RR) type when writing the zone database to file. The event data is applicable RR type.

3162

Microsoft-Windows-DNS-Server-Service

The DNS server encountered an unknown protocol while writing a well-known service (WKS) resource record to the zone file. The event data is the protocol number.

3163

Microsoft-Windows-DNS-Server-Service

While writing a well known service (WKS) record to the zone file, the DNS server encountered a port number that is not associated with a known service. The event data is the port number of the unknown service.

5105

Microsoft-Windows-DNS-Server-Service

The DNS server attempted to cache an CNAME (alias) resource record for the domain node. The operation failed, since the CNAME RR must be the only RR for its domain name.

5106

Microsoft-Windows-DNS-Server-Service

The DNS server attempted to cache an CNAME (alias) resource record (RR) for a domain name with existing RRs. The CNAME RR is ignored, since it must be the only RR for its domain name.

5107

Microsoft-Windows-DNS-Server-Service

The DNS server created CNAME (alias) loop caching CNAME resource records (RRs). The record is ignored, since CNAME loops are not allowed.

5108

Microsoft-Windows-DNS-Server-Service

The DNS server created an CNAME (alias) loop loading CNAME at %1. One link in CNAME loop: DNS name %2 is an alias for CNAME %3. See adjoining messages for other links in the CNAME loop.

6527

Microsoft-Windows-DNS-Server-Service

Zone %1 expired before it could obtain a successful zone transfer or update from a master server acting as its source for the zone. The zone has been shut down.

6530

Microsoft-Windows-DNS-Server-Service

During transfer of zone %1 from master at %2, the DNS server received a resource record (RR) for domain node %3 at which an CNAME (alias) RR was already received. When used, the CNAME RR must be the only record for its domain name. The CNAME RR for %3 will be ignored.

6531

Microsoft-Windows-DNS-Server-Service

During transfer of zone %1 from master at %2, the DNS server received a CNAME (alias) resource record (RR) for domain node %3 for which other records of that name were already received. When used, the CNAME RR must be the only record for its domain name. The CNAME RR for %3 will be ignored.

6532

Microsoft-Windows-DNS-Server-Service

During transfer of zone %1 from master at %2, the DNS server received a CNAME (alias) resource record (RR) for domain node %3 which would form an CNAME loop if accepted and used. The CNAME RR for %3 is being ignored.

6702

Microsoft-Windows-DNS-Server-Service

DNS server has updated its own host (A) records. In order to ensure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update. An error was encountered during this update, the record data is the error code.

If this DNS server does not have any DS-integrated peers, then this error
should be ignored.

If this DNS server's Active Directory replication partners do not have the correct IP address(es) for this server, they will be unable to replicate with it.

To ensure proper replication:
1) Find this server's Active Directory replication partners that run the DNS server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this server.
5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact. (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the Active Directory DNS server you are updating.)
6) Note, that is not necessary to update EVERY replication partner. It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data.

7600

Microsoft-Windows-DNS-Server-Service

The global query block list is a feature that prevents attacks on your network by blocking DNS queries for specific host names. This feature has caused the DNS server to fail a query with error code NAME ERROR for %1 even though data for this DNS name exists in the DNS database. Other queries in all locally authoritative zones for other names that begin with labels in the block list will also fail, but no event will be logged when further queries are blocked until the DNS server service on this computer is restarted. See product documentation for information about this feature and instructions on how to configure it.

Below is the current global query block list (this list may be truncated in this event if it is too long):
%2

Related Management Information

DNS Server

DNS Infrastructure

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft