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

DNS TCP fallback: firewall blocks truncated-answer recovery

Small A-record lookups work, but a larger response fails from one office. Someone suggests shortening the hostname. The hostname declines to comment.

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: Lab DNS client retries truncated UDP responses over TCP. Captures are on the same affected path; response-size policy is supplied explicitly.

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

Small A-record lookups work, but a larger response fails from one office. Someone suggests shortening the hostname. The hostname declines to comment.

Checks to compare

  1. Capture transport transition. Compare what this check establishes with the other devices in the path.
  2. Inspect policy and resolver listener. Compare what this check establishes with the other devices in the path.
  3. Validate corrected path. Compare what this check establishes with the other devices in the path.

Scope matters. Lab DNS client retries truncated UDP responses over TCP. Captures are on the same affected path; response-size policy is supplied explicitly.

Reveal the diagnosis, common mistakes and next action

What the evidence supports

Truncation is an instruction to retrieve the complete response over an appropriate supported path. The firewall evidence locates the block here.

Common mistakes to avoid in this scenario

  • The EDNS payload should always be increased: Force larger UDP responses without allowing the required TCP fallback.
  • The record is missing from the zone: Recreate the record even though an authoritative TCP query already returns it.

A proportionate next action

Permit the intended DNS TCP path through change control, then test both transports and large responses.

Limits of the conclusion

Large DNS failures can also involve fragmentation, MTU or server behaviour. TC, SYN and policy-counter evidence distinguish this scenario.

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