Investigating Intermittent DNS Resolution Issues

Incident Report for Rebel

Postmortem

Headline: [RESOLVED] DNS Resolution Routing Issue
Date: March 4, 2026

Summary:
Earlier today, some active domains intermittently resolved to incorrect "parked" pages or IP addresses.

Root Cause:
During a scheduled infrastructure upgrade, a configuration error caused a segment of traffic for active domains to be temporarily processed by a nameserver designated for expired/parked services. This resulted in "parked" IP addresses being served to users despite the domains being in good standing.

Resolution:
Our Engineering team has isolated the expired domain DNS service from the production network. All resolution is now correctly originating from our production clusters.

Note on Propagation:
Standard DNS caching (TTL) may cause these "parked" records to persist for some users for up to 60 minutes. Clearing your browser cache or flushing your local DNS will help refresh the connection immediately.

Thank you.

Posted Mar 04, 2026 - 14:38 EST

Resolved

This incident has been resolved.

Posted Mar 04, 2026 - 14:37 EST

Monitoring

Our Engineering team has identified and corrected the synchronization error affecting our nameserver clusters. All DNS records (A, CNAME, etc.) are now correctly configured on our global nodes.

What to Expect: While the fix is live on our end, you may experience intermittent connectivity as the corrected records propagate across the internet. This is due to standard DNS caching (TTL) and typically resolves within the hour.

Verification: To confirm your domain is resolving correctly, we suggest checking it via a third-party tool like DNSChecker.org. Once you see the "Green Checks" reflecting your correct IP address globally, your local services should be fully restored.

Final Update: We are continuing to monitor the stability of the sync to ensure no further disruptions occur.

Posted Mar 04, 2026 - 10:26 EST

Identified

We are responding to an emergency issue affecting DNS accuracy across the Rebel Nameserver network.

The Problem: A synchronization failure is causing a subset of domains to resolve to incorrect external records. This results in intermittent website "Not Found" errors, incorrect site loading, and email delivery failures.

Our Action: We are forcing a fresh zone-file synchronization across all secondary nameserver nodes and performing a global cache purge. We are working to restore 100% resolution accuracy as our highest priority.

Posted Mar 04, 2026 - 10:20 EST