Investigating DNS Resolution & Routing Issues

Incident Report for Internic Status Page

Postmortem

[RESOLVED] DNS Resolution Routing Issue

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:39 EST

Resolved

This incident has been resolved.

Posted Mar 04, 2026 - 14:39 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:25 EST

Identified

We are currently investigating an issue affecting DNS resolution for domains utilizing Internic Nameservers.

The Problem: We have identified a synchronization error affecting our nameserver clusters. This is causing some DNS records (including A records and CNAMEs) to intermittently resolve to incorrect external destinations.

Our Action: Our Engineering team is actively re-synchronizing our global nameserver nodes and purging caches to restore correct routing. If your website, email, or other connected services are currently unreachable, this is the root cause.

Posted Mar 04, 2026 - 10:22 EST