Nope - because it's a secondary of an existing zone. The master will provide all information, and you cannot add or modify records in a Secondary, as all information comes from the Master. In this case, the master is the _MSDCS zone.
Rick Kingslan MCSE, MCSA, MCT Microsoft MVP - Active Directory Associate Expert Expert Zone - www.microsoft.com/windowsxp/expertzone -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Salandra, Justin A. Sent: Monday, September 01, 2003 8:48 AM To: '[EMAIL PROTECTED]' Subject: RE: [ActiveDir] _MSDCS They currently all point to themselves. When you did it, did you have to recreate the data in the _msdcs zone? -----Original Message----- From: Rick Kingslan [mailto:[EMAIL PROTECTED] Sent: Saturday, August 30, 2003 12:45 PM To: [EMAIL PROTECTED] Subject: RE: [ActiveDir] _MSDCS More importantly, the ForestDNS zone in DNS is just this. As I understand it, and anyone correct me if I'm wrong, the reason for doing this (the classic DNS island problem) is not present in Win2k3 if the ForestDNS zone is left. As to what you're doing - I've done it many times successfully - and I'm not sure what you're doing wrong, Justin. Are you re-pointing the IP of the DCs and DNS servers to themselves once done? Look here: http://support.microsoft.com/default.aspx?scid=kb;en-us;275278 Good luck! Rick Kingslan MCSE, MCSA, MCT Microsoft MVP - Active Directory Associate Expert Expert Zone - www.microsoft.com/windowsxp/expertzone -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Salandra, Justin A. Sent: Saturday, August 30, 2003 9:30 AM To: ActiveDir (E-mail) Subject: [ActiveDir] _MSDCS Question I tried to split out the _MSDCS.forestname.org as a separate zone so that I could replicate that zone forest wide to ensure high availibitly of the zone. It is a best practice I learned in the Microsoft 2210 Workshop. When I did this the _MSDCS sub domain under the forestname zone became a delegation, like it is suppose to be. The new zone was created but it was missing all the information you would find in the _MSDCS sub domain. Now in WIndows Server 2003, if you did this, the information followed and populated the new zone automatically. Since I was missing all the info, I deleted the new zone and the _msdcs sub domain and then recreated the sub domain _msdcs under the forestname zone. I then had to do a ipconfig/ flushdns on each and every domain controller, net stop and net start the Netlogon service, the KDC, and the FRS and hope and pray that it populated the zone automatically again. For some of the servers I had to manually put back the, I think it is called, the DSA record. The CNAME records you find in the root of the _msdcs subdomain. It looks like thier GUID. Has anyone tried to do this and if so have you been successful? What steps did you follow? I used replmon and verified that there were no replication errors, so I think I am back to where I was before. Justin A. Salandra, MCSE Senior Network Engineer 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/ 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/ 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/ 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/
