DNSimple incident

Intermittent DNS Resolution for Certain ALIAS Records

Minor Resolved View vendor source →

DNSimple experienced a minor incident on February 18, 2026 affecting Name Servers, lasting 1h 42m. The incident has been resolved; the full update timeline is below.

Started
Feb 18, 2026, 02:24 PM UTC
Resolved
Feb 18, 2026, 04:07 PM UTC
Duration
1h 42m
Detected by Pingoru
Feb 18, 2026, 02:24 PM UTC

Affected components

Name Servers

Update timeline

  1. monitoring Feb 18, 2026, 02:24 PM UTC

    Starting at 08:35 UTC, we are experiencing intermittent DNS resolution issues affecting a subset of ALIAS records that point to hostnames within the same zone. Earlier today, we began rolling out improvements to our alias resolution handling. During the deployment, a bug was introduced that manifests when an ALIAS record targets a name inside its own zone. Because the updated logic is not yet fully deployed across all authoritative nameservers, affected records may resolve inconsistently depending on which nameserver handles the query. This is resulting in sporadic resolution degradation for impacted ALIAS records. We have identified the issue and are currently rolling back the changes across the affected authoritative nameservers. We are actively monitoring resolution behavior as the rollback progresses. We will provide further updates once the rollback is fully complete and resolution behavior has stabilized. We apologize for the disruption and appreciate your patience.

  2. resolved Feb 18, 2026, 04:07 PM UTC

    The rollback has completed, and DNS resolution has returned to normal behavior. We will be making follow-up improvements to alias-resolution handling, including additional safeguards and testing to prevent recurrence.