Microsoft KB Archive/250488

From BetaArchive Wiki
Knowledge Base

Problems with DNS Zone Transfers that Included Unicode Characters

Article ID: 250488

Article Last Modified on 11/1/2006


  • Microsoft Windows NT Server 4.0 Standard Edition
  • Microsoft Windows NT 4.0 Service Pack 1
  • Microsoft Windows NT 4.0 Service Pack 2
  • Microsoft Windows NT 4.0 Service Pack 3
  • Microsoft Windows NT 4.0 Service Pack 4
  • Microsoft Windows NT 4.0 Service Pack 5
  • Microsoft Windows NT 4.0 Service Pack 6
  • Microsoft Windows NT 4.0 Service Pack 6a

This article was previously published under Q250488


A Microsoft Domain Name Server (DNS) configured as a secondary DNS server may fail to complete a zone transfer from a Windows 2000 DNS server that has resource records with unicode strings. Also, the server may fail to load the complete zone.


Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.


Request For Comment (RFC) 2181 states that any binary string may be used in the label of any resource record. A zone transfer should complete, even with resource records that are not standard ASCII characters.

Additional query words: primary rr

Keywords: kbhotfixserver kbqfe kbnetwork kbprb KB250488