Overview

Moving to a new host requires DNS updates that must be handled carefully to avoid unnecessary downtime.

Symptoms

• Users report inconsistent or failed access to the affected service, device, or application.
• Normal business or home workflows are interrupted, delayed, or no longer reliable.
• The issue may be isolated to one user or may affect multiple systems depending on the root cause.

Cause

Incomplete record migration, missed subdomains, high TTL values, or rushed cutovers often create service interruptions.

Resolution

Inventory existing records, lower TTL in advance, prepare the new hosting environment, update DNS at the right time, and validate site, email, and SSL services after the move.

1. Confirm the exact symptoms and identify who or what is affected.
2. Check for recent changes such as updates, password changes, hardware swaps, DNS changes, or policy adjustments.
3. Test the most likely root cause first and document all findings clearly.
4. Apply the corrective action in the least disruptive way possible and verify the issue is fully resolved.
5. Record the final outcome, any user communication, and any recommended follow-up work.

Prevention

Use a written cutover checklist and verify all key records before pointing production traffic to the new host.

When to Contact Support

If the issue continues after standard troubleshooting, affects multiple users, involves data loss risk, or raises security concerns, it should be escalated to a qualified technician promptly.