The reason behind the issue with DNS resolution was due to the change of the nameserver for the learn2earn domain. (SUP-1491)

The platform was spun-up manually after the system reboot. Automatic platform deployment after reboot was disabled pre-emptively, to stop any recurring platform deployments that might cause corruption of data.

We are waiting on the response from the learning centre for the root cause of DNS Issue.

The incident was due to a DNS lookup failure causing to report downtime from multiple global locations. After several intermittent failures and recoveries across regions like Europe, Asia, and North America, the DNS issue was finally resolved automatically.

We will be inquiring the learning centre about this incident root cause.

The domain lacks a valid NS (Name Server) record. The dig command for retrieving NS records returns a NXDOMAIN status, indicating that the domain does not exist or is not properly configured. The authority section of the response contains a SOA (Start of Authority) record, which suggests that the domain exists, but it lacks a valid NS record.

Generally, a valid NS record is necessary for DNS resolvers to locate the authoritative name servers for a domain. Without a valid NS record, DNS resolvers may fail to resolve the domain correctly, leading to issues with DNS resolution.