Domain Controller demotion failed (DC=ForestDnsZones...)

[Billie]

After I was running DCpromo then I got the below error message:

Active Directory could not find another domain controller to transfer the remaining data in directory partition DC=ForestDnsZones,DC=business,DC=auburn,DC=edu.

"The specified domain either does not exist or could not be contacted."

I am on a Windows 2003 domain controller. It was just a few months ago the only DNS. The DNS has the zones required for Active directory and one secondary zone. This server is not a global catalog, and will not hold any of the 5 FSMO roles. After using dcdiag and replmon replication is working as it should between this and out 2 other DCs. Can anyone please help.

[Rawko]

The proper way it to use the /forceremoval switch. It is a trivial an safe matter to cleanup the metadata after the fact. You just need to follow the below procedure in the article:
http://support.microsoft.com/kb/216498

[Big Fish]

Could you tell us why you dont want a GC in the environment? Is your other DNS server AD integrated or not?

[Jerry]

The error seems to be a warning to let you know that you should prevent data from losing, where this mechanism not in place, you would lose many of your AD representative DNS zones. Before making a recommendation on how to proceed I want to know what your goals are in demoting this DC, which I understand it is the only DNS server you have?