DNS Server Message Processing
Applies To: Windows Server 2008 R2
These events represent problems processing data received by the DNS server that may or may not have a negative effect on server functionality.
Events
| Event ID | Source | Message |
|---|---|---|
Microsoft-Windows-DNS-Server-Service |
The DNS server received an invalid DNS query from %1. The query was rejected or ignored. The event data contains the DNS packet. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server encountered a bad packet from %1. Packet processing leads beyond packet length. The event data contains the DNS packet. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server received a bad TCP-based DNS message from %1. The packet was rejected or ignored. The event data contains the DNS packet. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server encountered an invalid domain name in a packet from %1. The packet will be rejected. The event data contains the DNS packet. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server encountered a domain name exceeding the maximum length in the packet from %1. The event data contains the DNS packet. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server encountered an invalid domain name offset in a packet from %1. The event data contains the DNS packet. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server encountered a name offset exceeding the packet length from %1. The event data contains the DNS packet. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server encountered a packet name exceeding the maximum label count from %1. The event data contains the DNS packet. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server encountered an invalid DNS update message from %1. The packet was rejected. The event data contains the DNS packet. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server encountered an invalid response message from %1. The packet was rejected. The event data contains the DNS packet. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server encountered a name with a label whose length exceeds the maximum of 63 bytes from %1. The event data contains the DNS packet. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server recv() function failed. The event data contains the error. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server recvfrom() function failed. The event data contains the error. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server send() function failed. The event data contains the error. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server sendto() function failed. The event data contains the error. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server select() function failed. The event data contains the error. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server accept() function failed. The event data contains the error. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server GetQueuedCompletionStatus() function failed. The event data contains the error. | |
Microsoft-Windows-DNS-Server-Service |
The DNS server encountered a packet addressed to itself on IP address %1. The packet is for the DNS name "%2". The packet will be discarded. This condition usually indicates a configuration error. Check the following areas for possible self-send configuration errors: 1) Forwarders list. (DNS servers should not forward to themselves). 2) Master lists of secondary zones. 3) Notify lists of primary zones. 4) Delegations of subzones. Must not contain NS record for this DNS server unless subzone is also on this server. 5) Root hints. Example of self-delegation: -> This DNS server dns1.example.microsoft.com is the primary for the zone example.microsoft.com. -> The example.microsoft.com zone contains a delegation of bar.example.microsoft.com to dns1.example.microsoft.com, (bar.example.microsoft.com NS dns1.example.microsoft.com) -> BUT the bar.example.microsoft.com zone is NOT on this server. Note, you should make this delegation check (with nslookup or DNS manager) both on this DNS server and on the server(s) you delegated the subzone to. It is possible that the delegation was done correctly, but that the primary DNS for the subzone, has any incorrect NS record pointing back at this server. If this incorrect NS record is cached at this server, then the self-send could result. If found, the subzone DNS server admin should remove the offending NS record. You can use the DNS server debug logging facility to track down the cause of this problem. |
|
Microsoft-Windows-DNS-Server-Service |
The DNS server failed to process a packet from %1. The packet was discarded. |