DDIENGINEER.COM / FICTIONAL NETWORKS. REAL TROUBLESHOOTING.NO PRODUCTION SYSTEMS WERE REBOOTED.
⌕ PACKET DETECTIVE
DNS · Foundation

Troubleshoot split DNS and VPN name resolution

The name with two addresses. Payroll works over the VPN but not from home without it. Both lookups return NOERROR. Someone has filed “DNS randomly wrong”. The word randomly is doing a great deal of work.

What you’ll practise

Inspect the supplied evidence, distinguish competing explanations and choose a proportionate next action. Use the clickable topology and private notebook to keep track of your findings.

Lab scope: payroll.ddiengineer.com is an internal-only application. The external service address is a deliberate holding page. Evidence uses two documented resolver views.

Validation: Fictional training scenario; not vendor-build verified. No live network access is required. Basic DNS, DHCP and IP addressing knowledge is helpful. Progress is stored in this browser.

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

Payroll works over the VPN but not from home without it. Both lookups return NOERROR. Someone has filed “DNS randomly wrong”. The word randomly is doing a great deal of work.

Checks to compare

  1. Inspect client DNS settings. Compare what this check establishes with the other devices in the path.
  2. Compare authoritative views. Compare what this check establishes with the other devices in the path.
  3. Check application path. Compare what this check establishes with the other devices in the path.

Scope matters. payroll.ddiengineer.com is an internal-only application. The external service address is a deliberate holding page. Evidence uses two documented resolver views.

Reveal the diagnosis, common mistakes and next action

What the evidence supports

The different answers match the documented internal and external views. The failing workflow is off-VPN access to an internal-only service, not evidence of a corrupt global record.

Common mistakes to avoid in this scenario

  • Global stale cache: Purge all DNS caches.
  • Duplicate A record: Delete the internal answer.

A proportionate next action

Explain the VPN requirement. Investigate VPN DNS configuration if a connected client still uses the external resolver.

Limits of the conclusion

Different answers alone do not prove split DNS. Here, resolver settings, view policy and application tests establish it.

Review the relevant platform documentation for the version and configuration in your environment.

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