Active Directory DNS: missing SRV records after migration
After a DNS migration, web browsing and server A-record lookups work, but new domain logons fail. Someone has declared DNS innocent on the strength of one ping.
What you’ll practise
Trace the supplied evidence, challenge alternative explanations, and choose a safe next action. Use the topology and private notebook to document your reasoning.
Lab scope: Isolated AD lab under ad.ddiengineer.com. Time sync, DC reachability and authentication services pass direct checks. Client discovery uses the new resolver path.
Validation: Original synthetic operational lab; not a reproduced vendor defect
DHCP says yes.
DNS says yesterday.
A laptop moved networks. Its name didn’t. Find out who’s telling the truth — and what you should check next.
Realistic DNS, DHCP and IPAM mysteries.
No lab setup. No production access. Just your judgement.
New lease.
Old address.
Same confused user.
10.62.4.27 ✓↓ six minutes and three cache flushes later09:36 / DNS ANSWER10.61.4.27 ?“Have you tried flushing it again?”
The fourth time is not a strategy.
Troubleshooting guide
Recognise the symptoms
After a DNS migration, web browsing and server A-record lookups work, but new domain logons fail. Someone has declared DNS innocent on the strength of one ping.
Checks to compare
- Compare old and new authorities. Compare what this check establishes with the other devices in the path.
- Validate DC and query path. Compare what this check establishes with the other devices in the path.
- Verify corrected discovery. Compare what this check establishes with the other devices in the path.
Scope matters. Isolated AD lab under ad.ddiengineer.com. Time sync, DC reachability and authentication services pass direct checks. Client discovery uses the new resolver path.
Reveal the diagnosis, common mistakes and next action
What the evidence supports
The failure is not ordinary host lookup. Missing SRV discovery data blocks clients locating the DC even though its A record is correct.
Common mistakes to avoid in this scenario
- Clients need a different public resolver: Replace the AD-aware resolver with a public DNS service to locate domain controllers.
- The application A record is sufficient: Keep the migration unchanged because direct host lookups work.
A proportionate next action
Restore the intended AD discovery records/delegation with the directory team, then test fresh discovery and authentication.
Limits of the conclusion
Not all logon problems are DNS. The case independently checks time, connectivity and authentication service health.