On a computer that is running Windows Server 2008 or Windows Vista, you cannot add one or more servers to the securelist of a DNS service instance that is hosted on a server that is running Windows 2000 or Windows Server 2003
Consider the following scenario:
- You install the Microsoft Remote Server Administration Tools on a computer that is running Windows Vista or Windows Server 2008.
- From this computer, you use the Dnscmd.exe tool or the DNS Management Microsoft Management Console (MMC) snap-in. You use one of these tools to manage a DNS service instance that is hosted on a server that is running Windows 2000 or Windows Server 2003.
- You try to add some secondary servers to the “allowed zone transfer server” list (securelist) of a primary DNS server zone.
In this scenario, the secondary servers are not added to the securelist as expected. Additionally, the symptoms that appear for this problem depend on the number of IP addresses that you try to add to the securelist. The following are the symptoms that may appear:
- If you try to add more than one IP address, the operation fails.
- If you try to add only one IP address of a secondary server, the operation seems to complete successfully. However, the operation adds an address of 220.127.116.11 to the securelist, instead of the expected IP address.
For example, you try to add a “18.104.22.168″ server and a “22.214.171.124″ server to the securelist by using the following command:
dnscmd <server name> /zoneresetsecondaries <zone name> /securelist 126.96.36.199 188.8.131.52
In this case, you receive the following error message:
Command failed: DNS_ERROR_INVALID_IP_ADDRESS 9552
If you try to add only the “184.108.40.206″ server to the securelist by using the following command, an IP address of “220.127.116.11″ is incorrectly added to the securelist instead of the “18.104.22.168″ address:
dnscmd <server name> /zoneresetsecondaries <zone name> /securelist 22.214.171.124
However, in this case, you receive no error message.
For more information on this issue, including potential causes, workarounds, and resolutions, see: Microsoft KB Article KB973245.