I recently promoted 3 servers to DCs on my existing single-domain, NT4 network. We did an in-place upgrade and decided to create a new DNS namespace for our internal corporation. We are keeping the old DNS zone for now and migrating clients and servers away from it. Public-facing apps will continue to exist in the old DNS zone. Both the new and old DNS zones are ADI and allow dynamic updates. We have a mix of 9x->XP clients. Servers are NT4 or W2K.
Here's what bothers me ... Some of the servers list the new DNS zone (xyz.net) as their domain and primary DNS suffix while others list the old NetBIOS domain (WIDGET) as their member domain with the primary DNS suffix listed as either the old DNS domain (abc.com) or <blank>. Of the servers that changed to the new DNS name, all are W2K - yet not all of the W2K servers show the change. Some W2K client PCs exhibit this change as well, but not all. I'm not having DNS issues since I've duplicated necessary records from the old DNS zone to the new. Not all of the servers and PCs have been restarted - not sure if only the restarted ones show the change. --------------------------------------- I'm wondering if this seems normal or if there anyone sees any problems with this until I can get everything moved to the new DNS zone. Dave K. List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
