DNS for Active Directory: why domain computers need internal DNS
Domain computers find domain controllers through DNS SRV records. Point them at public DNS and sign-in, policy and drive maps quietly break.
- Level
- Intermediate
- Length
- About 45 minutes
- Contents
- 3 lessons · 1 video · final exam
- Status
- Published · updated 1 Oct 2026
Skills you'll practise
- Explain how a domain computer finds a domain controller using DNS SRV records
- Diagnose DC-location failures with nslookup and nltest /dsgetdc
- Fix client DNS settings safely and verify the result
Course outline
- 1.DNS for Active Directory: why domain computers need internal DNSVideo · 5 min
- 2.How a domain computer finds a domain controllerLesson · 14 min
- 3.How the Windows DNS client asks, caches and fails overLesson · 14 min
- 4.Dynamic registration, stale records and reverse lookupsLesson · 12 min
- 5.DNS for Active Directory: why domain computers need internal DNS: knowledge checkKnowledge check · 25 questions
- 6.DNS for Active Directory: why domain computers need internal DNS: practical exerciseKnowledge check · 1 question
- 7.VPN connected, but no file sharesScenario
- 8.Final exam5 questions · passing it completes the course, so people who already know the material can test out
Sources it draws on
The lessons and questions are written from these references, so learners can go back to the original.
- Microsoft Learn: How domain controllers are located in Windows
- Microsoft Learn: Troubleshoot domain controller location issues
- RFC 2782: A DNS RR for specifying the location of services (DNS SRV)
See it with your own jobs and topics
Tell us about your team and we'll walk you through setup, from choosing jobs to your first skills check.