Microsoft AD and the retro information melt down

On two separate projects in two separate companies I have become aware of an issue where AD information from a long time ago, seems to revert back into AD.  In case A, a DC had been removed several months prior, and then Bam!   it looked like there references in AD to the "flying dutchman" AD server.  In case b, the event seems to revolve around a switch reboot.   In this case AD information from YEARS ago returned (We think the information coincides to the point when the systems were imaged and first brought into the domain (like 6 years ago))  I did note that one of the DC was not responding to dns queries via nslookup, and workstations on a specific subnet seemed to revert from DHCP subnet IP to a 169 address.  Immediately after the event rebooting the workstations still left the system with the 169 addresses.  The switches involved are Cisco switches and the subnet has an IP helper for the interface.

I don't have specifics on what happened, I am just trying to understand what causes an event like this.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Shaun VermaakTechnical SpecialistCommented:
Seems like a replication problem that went unnoticed? To actually have this behaviour, you would need to set a bunch of flags (such as lingering objects and tombstoned age), usually only done during troubleshooting.

Always check with this command
repadmin /showrepl * > out.txt

Open in new window

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Michael B. SmithManaging ConsultantCommented:
Using dcdiag can also help in diagnosing badly behaved DCs.
the_b1ackfoxTechnophileAuthor Commented:
I appreciate both of your responses.  This increases both my "technical issue vocabulary" and ability to identify what is going on.  On the negative side I am still an empty husk inside because I will be able to sound brilliant... for a moment...  and then have nothing further, lol (I guess I have some blanks to work on filling in)
Shaun VermaakTechnical SpecialistCommented:
I guess I have some blanks to work on filling in
We will be more than happy to assist you during this "journey" ;)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.