Cannot Manually Add SRV Records to a Delegated Subzone

When you attempt to manually add an SRV resource record in a delegated subzone by using the Windows 2000 DNS snap-in, an additional subdomain is created and the record is placed in the subzone of this subdomain rather than the delegated subzone.

For example, if the zone example.com is located on a third-party DNS server, and the following subzone is delegated to a Windows 2000 DNS server: when you attempt to add an SRV record in this zone manually, for example, _rvp, the following record is created: The following record should be created instead:

When you use the Windows 2000 DNS snap-in, you are only able to create SRV resource records from a server that is the authority for the entire domain, not just the delegated subzone.

To resolve this issue, use either of the following methods:

• If the delegated subzone is a standard primary zone, stop the DNS Server service on the server and edit the zone file to add the SRV record. In the example that was used in the "Summary" section, the zone file would be:
  %SystemRoot%\System32\Dns\_tcp.Example.com.dns
  After you add the proper record to the zone file, restart DNS Server.
• If the zone is an Active Directory-integrated zone, use the Dnscmd.exe utility in the Windows 2000 Support Tools to add the record. In the example that was used in the "Summary" section, the proper record is created by using the following command:
  dnscmd /recordadd _tcp.example.com _rvp srv 0 0 79 server1.example.com

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

If you are creating an SRV resource record on a server which is the authority for the entire domain of example.com, right-click example.com, click Other New Record, and then click the record type SRV. You are then able to continue creating an SRV resource record.

For additional information, click the article number below to view the article in the Microsoft Knowledge Base: