When DNS was the real bug

How split DNS and VPN paths can masquerade as an application outage until resolution is aligned across offices and remote workers.

Meridian Outfitters is a stand-in label for a retailer whose “app down” tickets spiked every Monday while application metrics stayed green.

What was actually wrong

Laptops on office Wi‑Fi resolved the public hostname to the corporate proxy. Remote workers resolved the same hostname to a legacy IP that bypassed the new path. The application was healthy; the answers were not consistent.

Half the team was debugging software; the other half was living in a different network reality.

We fixed it by making internal resolution explicit and boring: local records aimed at the right edge, one canonical path documented, and a single test page everyone could hit to prove “this is what good looks like.”

Time and money

Support hours dropped once tickets stopped chasing ghosts. The lesson is not “DNS is magical”—it is that alignment is cheaper than heroics.

Note: Names, numbers, and timeline are anonymized or blended from similar engagements; the split-DNS pattern is representative of field work.

If you want help auditing that kind of alignment, reach out.