[2026-01-28] DNS Issues¶
Date: 2026-01-28
Author: Trond H. Amundsen
Summary¶
Some DNS domains that were delegated to the NREC name servers and administered with the NREC DNS Service, failed to resolve for approximately one hour starting at 11:45 CET.
Description¶
NREC changed its name from “UH-IaaS” to “NREC” a few years ago, and a
new DNS domain nrec.no was also aquired to replace the obsolete
uh-iaas.no domain. The domain uh-iaas.no had been working in
parallel since the name change, and we decided that it was time to
remove all records in the old domain.
We failed to recognize that some delegated domains still used the old
addresses for the authoritative name servers (ns1.uh-iaas.no and
ns2.uh-iaas.no). The unintended and unforeseen consequence was
that these domains failed to resolve when records in the
uh-iaas.no domain were removed.
Timeline:
11:45 CET: All records in the DNS zone
uh-iaas.noare removed12:09 CET: The first issues with DNS in NREC are reported. The NREC team quickly identifies the problem and decides on a solution
12:45 CET: Records
AandAAAAforns1.uh-iaas.noandns2.uh-iaas.noare restored in theuh-iaas.nozone
The perceived timeline for customers may differ from the one above, due to local cache on their respective resolvers.
Consequences¶
DNS zones that was delegated a long time ago were using the old nameserver names. These zones failed to resolve for approximately one hour.
How could this be avoided?¶
We could and should have recognized that zone delegation would be a potential issue.
Could we have handled the issue better?¶
Not really. We monitored the situation for potential issues after
deleting records from the uh-iaas.no domain, and were quick to
respond when problems were reported.
Mitigation Measures¶
We will follow this procedure in order to avoid this problem in the future:
Identify which delegated zones use the old DNS server names
Contact the owners of the zones in question and ask them to change the delegation to using the new (correct) DNS server names
When all delegated zones have been verified as using the correct DNS server names, empty the
uh-iaas.nozone