<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>[Apologies for duplicate emails]</div><div><br></div>Dear colleagues,<br><br>This morning, the RIPE NCC briefly experienced a problem on the<br><a href="http://ripe.net/">ripe.net</a> DNS servers. Operation of K-root and other public DNS<br>services was not impacted at any time during this outage.<br><br>At 11:45 UTC this morning, an error in the deployment script used<br>to update the <a href="http://ripe.net/">ripe.net</a> zone caused a partial zone file to be activated.<br>This caused the <a href="http://ripe.net/">ripe.net</a> DNS servers to return NX-domain responses<br>for some valid hosts and/or subdomains in the <a href="http://ripe.net/">ripe.net</a> zone, which<br>effectively rendered some of the RIPE NCC services unavailable during<br>this period.<br><br>DNS resolution for <a href="http://ripe.net/">ripe.net</a> was fully restored at 12:15 UTC. Caching<br>of the erroneous responses may have caused reachability problems until<br>13:15 UTC.<br><br>The error in the script has been identified and is only triggered in<br>a specific corner case. This error will be corrected today.<br><br>We apologise for any inconvenience caused.<br><br>Incident start: 05-Mar-2013 11:45:01 UTC<br>Incident end: 05-Mar-2013 12:14:58 UTC<br><div><br></div><div>Regards,</div><div><br></div><div>Romeo Zwart</div><div>GII Services Manager</div><div>RIPE NCC</div><div><br></div></body></html>