If I understand you correctly, it sounds like one or more domain controllers
were promoted into the xxxxxx.cm domain. I find this hard to believe, since
the same type-o would have to have been entered several times (while
promoting the DC(s) and while joining the PC(s) to the domain). I think that
DHCP is the much more likely culprit.

Questions:
What is your AD topology?
How many trees are in the AD forest?
How many domains/sudomains are in each tree?

----------
For now I'm going to assume that you have a single AD domain. Therefore, you
should be dealing with only one AD domain name.

Questions:
Is your AD domain name the same as your Internet domain name (i.e. email
address)?
How many DCs do you have?

Check the TCP/IP configuration on each DC (ipconfig /all).
What is the "Primary Dns Suffix" for the active /connected NIC?

I re-read your original post. So there is a xxxxxx.cm forward look up zone
on your DNS servers. Therefore, you must have accidentally promoted one or
more DCs into this domain. Once these DCs are found, and demoted, you will
be able to delete the xxxxxx.cm forward lookup zone.

If you find any DCs that have been promoted into xxxxxx.cm domain, you need
to demote them., verify their "Primary DNS Suffix of this Computer" setting,
and then re-promote them into the xxxxxx.com domain.




"Muhammad Essa" <MuhammadEssa@discussions.microsoft.com> wrote in message
news:BD6A1A64-6CE5-4D42-82FE-27F0D9CFE8AE@microsoft.com...
> Hi:
> Thanks for reply. I followed the steps and these mentioned steps were
> followed before as well now the main problem is with additional domain
> controllers where primary AD recognize some of them as .cm and some of
> them
> as .com ( Registered as ). How to solve the problem from the root so this
> may
> not occur next time. But from the initail point before creating another
> forward lookup zone.How a domain can pickup wrong domain name?
>
> thanks
> --
> Essa