Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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

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

View products that this article applies to.

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 IP_Address. 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 "More Information" 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.

↑ Back to the top

Cause

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

↑ Back to the top

Resolution

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

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.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, 32-bit versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Dns.exe5.2.3790.2718442,88007-Jun-200600:56x86SP1SP1QFE
W03a2409.dll5.2.3790.271825,08807-Jun-200600:52x86SP1SP1QFE
Windows Server 2003, x64-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Dns.exe5.2.3790.2718759,29606-Jun-200615:04x64SP1SP1QFE
W03a2409.dll5.2.3790.271825,60006-Jun-200615:04x64SP1SP1QFE
Wdns.exe5.2.3790.2718442,88006-Jun-200615:04x86SP1WOW
Ww03a2409.dll5.2.3790.271825,08806-Jun-200615:04x86SP1WOW
Windows Server 2003, Itanium-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Dns.exe5.2.3790.27181,125,88806-Jun-200615:04IA-64SP1SP1QFE
W03a2409.dll5.2.3790.271824,06406-Jun-200615:04IA-64SP1SP1QFE
Wdns.exe5.2.3790.2718442,88006-Jun-200615:04x86SP1WOW
Ww03a2409.dll5.2.3790.271825,08806-Jun-200615:04x86SP1WOW

↑ Back to the top

Status

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

↑ Back to the top

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

↑ Back to the top

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

↑ Back to the top

Keywords: kbautohotfix, kbwinserv2003sp2fix, kbwinserv2003presp2fix, kbbug, kbfix, kbqfe, KB920162

↑ Back to the top

Article Info
Article ID : 920162
Revision : 4
Created on : 10/9/2011
Published on : 10/9/2011
Exists online : False
Views : 318