Domain controllers: the server every login depends on
▶ Start the interactive lesson
Tuesday, 9:02. The service desk phones light up at once: nobody can log in, the file shares ask for passwords, and the printers have vanished. Your team lead doesn't look at a single laptop. She opens one console and says: "Both domain controllers in this site are down. Everything else is fine, it…
What a domain controller does
In a Windows business network, accounts live in a directory called Active Directory (AD). The servers that run it are domain controllers (DCs).
Passwords aren't stored or sent as text
The password itself doesn't travel across the network. The laptop uses it to answer a challenge, and the DC checks the answer against a hash it keeps for every account: users, admins and computers.
Several DCs, always in sync
Companies run at least two DCs, often more across sites. They replicate: a password change or a new user on one is copied to the others within minutes. If one fails, the others carry on.
How teams protect them
Very few domain admins. Day-to-day work uses normal accounts. Admin rights are a separate account used only when needed.
Key points
- Domain controllers run Active Directory and check every login, share and policy. If they're down, everything feels broken.
- They store a hash for every account and replicate with each other. That makes them, and their backups, the most sensitive systems you have.
- Protect them: few admins, separate admin machines, patch first, monitor replication, offline backups.
Words you'll learn
Active Directory (AD) · Domain controller (DC) · Hash · Replication · DCSync · Group Policy (GPO) · PAW (privileged access workstation)