Internal website resolves to old server for one subnet only

Minimal guidance for messy support realities.

Scenario

Most office users reach the new internal site, but one subnet still resolves to the retired host.

Recommended Resolution Path

  1. Identify which DNS server the affected subnet is actually using.
  2. Check stale records, conditional forwarders, or local resolver overrides in that segment.
  3. Flush caches on a test endpoint after server-side cleanup.
  4. Update subnet-specific documentation so future cutovers include that resolver path.

Technician Notes

Confirm the result, document the root cause, and record any preventative action worth standardizing.