CPSA ยท Windows domain reconnaissance and Active Directory
Active Directory reliance on DNS and LDAP
SRV records, domain controller discovery and LDAP queries against AD.
Key points
- Active Directory finds domain controllers through DNS.
- SRV records: clients query _ldap._tcp.dc._msdcs.<domain>; reserved _msdcs locates DCs and Kerberos servers by role.
- Next: the client resolves the hostnames and talks LDAP (TCP 389, 636 for LDAPS).
- Tester: an SRV query lists the DCs, ldapsearch queries them.
- Defences: restrict DNS zone transfers, authenticated and protected LDAP, segmented access to DCs.
Practice questions
Which DNS name lets a client locate a domain controller of the domain example.local?
- _ldap._tcp.dc._msdcs.example.local
- _http._tcp.example.local
- _smtp._tcp.mail.example.local
- _ntp._udp.time.example.local
Show answer
Answer: A. _ldap._tcp.dc._msdcs.example.local
The _ldap._tcp.dc._msdcs SRV name is the one for finding domain controllers. The others advertise web, mail or time services.
Which statements about AD, DNS and LDAP are correct?
- Clients use SRV records to find domain controllers
- The _msdcs subdomain helps locate DCs by role
- Domain join works the same with no working DNS
- LDAP uses TCP 389 and LDAPS uses TCP 636
- LDAP queries are carried over UDP 53
Show answer
Answer: A. Clients use SRV records to find domain controllers, B. The _msdcs subdomain helps locate DCs by role, D. LDAP uses TCP 389 and LDAPS uses TCP 636
SRV records and _msdcs drive DC discovery, and 389/636 are the LDAP and LDAPS ports. AD needs functional DNS, and LDAP does not run over port 53.
A DNS outage does not affect domain logons because credentials live in the AD database.
Show answer
Answer: False
False. Clients must find a domain controller through DNS SRV records first, so broken DNS breaks logon and domain services even if the DCs are healthy.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
