Microsoft KB Archive/920162

= Event 5504 is logged when a Windows Server 2003-based DNS server receives a packet that contains a DNAME resource record =

Article ID: 920162

Article Last Modified on 10/11/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Server 2003, Standard x64 Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, Datacenter x64 Edition
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
 * Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems

-





SYMPTOMS
When a Microsoft Windows Server 2003-based DNS server receives a packet that contains a DNAME resource record, the following event is logged in the DNS log: Event Type: Information

Event Source: DNS

Event ID: 5504

Description: The DNS server encountered an invalid domain name in a packet from. The packet will be rejected. The event data contains the DNS packet.

Note Event ID 5504 may also be logged because of other DNS packets. If event ID 5504 is related to a DNAME record, it can only be viewed in a network trace. The &quot;More Information&quot; section contains an example of how this network trace may look. The resolution that is provided in this article only applies to DNS event ID 5504 together with DNAME records.



CAUSE
This problem occurs because Windows Server 2003 does not support DNAME resource records as specified in Request for Comments (RFC) 2672.



Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003

Hotfix information
The hotfix that is contained in KB920162 will change the behavior of Windows Server 2003. The DNS server will accept packets that contain a DNAME resource record. Then the DNS server will forward the related CNAME record to the client if the forwarder's answer contains a CNAME record. The KB920162 hotfix will not add full DNAME support to Windows Server 2003 as specified in Request for Comments (RFC) 2672.

Prerequisites
To apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) installed.

Restart requirement
You do not have to restart your computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003, Itanium-based versions


STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section. This problem was first corrected in Windows Server 2003 Service Pack 2.



MORE INFORMATION
For more information about the terms that are used in this article, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates



When you take a network trace on the Windows Server 2003-based DNS server, the trace resembles the following: Frame 1 IP, Src: DNSClient, Dst: DNSServer UDP, Src Port: 1181, Dst Port: 53 Domain Name System (query) Transaction ID: 0x0017 Flags: 0x0100 (Standard query) Questions: 1 Answer RRs: 0 Authority RRs: 0 Additional RRs: 0 Queries www.SpecialName.com: type A, class IN

Frame 2 (72 bytes on wire, 72 bytes captured) IP, Src: DNSServer, Dst: DNSForwarder UDP, Src Port: 1699, Dst Port: 53 Domain Name System (query) Transaction ID: 0x2818 Flags: 0x0100 (Standard query) Questions: 1 Answer RRs: 0 Authority RRs: 0 Additional RRs: 0 Queries www.SpecialName.com: type A, class IN

Frame 3 (176 bytes on wire, 176 bytes captured) IP, Src: DNSForwarder, Dst: DNSServer UDP, Src Port: 53, Dst Port: 1699 Domain Name System (response) Transaction ID: 0x2818 Flags: 0x8580 (Standard query response, No error) Questions: 1 Answer RRs: 3 Authority RRs: 1 Additional RRs: 1 Queries www.SpecialName.com: type A, class IN   Answers SpecialName.com: type DNAME, class IN, dname StandardName.com www.SpecialName.com: type CNAME, class IN, cname www.StandardName.com www.StandardName.com: type A, class IN, addr 192.168.0.1 Authoritative nameservers StandardName.com: type NS, class IN, ns NS.StandardName.com Additional records NS.StandardName.com: type A, class IN, addr DNSForwarder

Frame 4 (72 bytes on wire, 72 bytes captured) Internet Protocol, Src: DNSServer (DNSServer), Dst: DNSClient (DNSClient) User Datagram Protocol, Src Port: 53 (53), Dst Port: 1181 (1181) Domain Name System (response) Transaction ID: 0x0017 Flags: 0x8182 (Standard query response, Server failure) Questions: 1 Answer RRs: 0 Authority RRs: 0 Additional RRs: 0 Queries www.SpecialName.com: type A, class IN

Additional query words: Server failure

Keywords: kbbug kbfix kbqfe kbpubtypekc kbhotfixserver kbwinserv2003presp2fix kbwinserv2003sp2fix KB920162

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.