DDIENGINEER.COM / FICTIONAL NETWORKS. REAL TROUBLESHOOTING.NO PRODUCTION SYSTEMS WERE REBOOTED.
⌕ PACKET DETECTIVE
DNS + AD / ADVANCED

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

DDIENGINEER.COM / INTERACTIVE NETWORK INVESTIGATIONS

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.

ADVANCED · DNS + DHCP · ~8 MIN

Realistic DNS, DHCP and IPAM mysteries.
No lab setup. No production access. Just your judgement.

01 Inspect the clues02 Build your theory03 Make the call
FEATURED / PD–009DNS + DHCP
THE LAPTOP WITH YESTERDAY’S ADDRESS

New lease.
Old address.
Same confused user.

09:30 / DHCP ACK10.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.

FIELD NOTES / READ BEFORE OR AFTER THE LAB

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

  1. Compare old and new authorities. Compare what this check establishes with the other devices in the path.
  2. Validate DC and query path. Compare what this check establishes with the other devices in the path.
  3. 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.

Read the technical reference →

Browse all investigations →

Browse troubleshooting case guides →The missing networkThe gap in the alibiThe record that refused to existThe name with two addressesThe office with no vacanciesThe relay to nowhereThe duplicate that wasn’tThe suspiciously quiet subnetThe laptop with yesterday’s addressThe security upgrade that broke renewalsThe container that couldn’t find anythingThe lease that rewrote historyThe intermittent DHCP lotteryThe edit that never reached DNSThe policy inherited from upstairsThe updater with the wrong badgeThe fixed address with no nameThe duplicate in another network viewThe update at the wrong front doorThe lease with no permission slipThe reservation the partner forgotThe immortal DNS recordThe pipeline that retried yesterdayThe route that outlived its resolverThe adjacency with no routeThe domain controller nobody could findThe backup with a missing keyThe green dashboard with the wrong answerThe two masters of one recordThe zone transfer with no guest listThe inventory that stopped at page oneThe allocation raceThe redundant pair on one plugThe answer too large for the doorThe IPv6 address with nowhere to go