DNS CNAME Name Resolution Does Not Work if a Record Lives in Delegated Subzone

• Microsoft Windows NT Server version 4.0

SYMPTOMS

When your computer resolves a name that you entered as a CNAME in DNS, you receive the following error messages

• When you try to ping the CNAME x like x.y.z.,where x.y.z. is a fully qualified domain name (FQDN):

  Bad IP address




• When you use Nslookup to resolve the CNAME x x like x.y.z.,where x.y.z. is a FQDN:

  Can't find x.y.z.: non-existent domain

CAUSE

This issue occurs because name resolution for CNAME records does not work when the corresponding "A" record resides in a delegated subzone.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next Windows NT 4.0 service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

   Date      Time      Size     File name   Platform
   -------------------------------------------------
   12/10/99  1:58 am   178,448  dns.exe     (Intel)
   12/10/99  1:57 am   299,792  dns.exe     (Alpha) 

WORKAROUND

In the zonefile, move the complete "zone records" section of the parent zone below the "delegated sub-zone" section.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article.

Additional query words:

Keywords : kbbug4.00 kbfix4.00
Version : winnt:4.0
Platform : winnt
Issue type : kbbug