{"id":640,"date":"2010-05-12T15:10:01","date_gmt":"2010-05-12T13:10:01","guid":{"rendered":"http:\/\/www.tld.sc\/en\/?p=640"},"modified":"2020-01-13T10:59:53","modified_gmt":"2020-01-13T08:59:53","slug":"what-went-wrong-at-the-de-registry-earlier-today","status":"publish","type":"post","link":"https:\/\/www.bnamed.blog\/en\/2010\/05\/what-went-wrong-at-the-de-registry-earlier-today\/","title":{"rendered":"What went wrong at the .de-registry earlier today?"},"content":{"rendered":"<p><img decoding=\"async\" loading=\"lazy\" class=\"alignright size-full wp-image-643\" title=\"deniclogo140x74\" src=\"http:\/\/www.tld.sc\/en\/wp-content\/uploads\/2010\/05\/deniclogo140x74.png\" alt=\"deniclogo140x74\" width=\"140\" height=\"74\" \/>From 13:30 through about 14:50 today, <a href=\"http:\/\/www.tld.sc\/en\/2010\/05\/problems-at-the-german-registry\/\">large parts of the .de zone where unavailable<\/a>, causing most if not all of the 13 million .de domain names with websites and e-mail to be unavailable. It is very uncommon for a large domain name extension to be fully unavailable, so much that it is causing domain names under that TLD to actually not work. In the last 5 to 10 years, as far as we know about, of all the large TLD&#8217;s only .nu, .se and .biz have known some real downtime.<\/p>\n<p>Insiders tell us that the nameserver infrastructure that is being used by DENIC is somewhat out-dated and certainly not in line with the requirements of a large TLD like .de. DENIC would still be using a mixure of the standard version of &#8220;BIND&#8221; and &#8220;NSD&#8221;\u00a0 as their nameserver software. While both are known to be very robust and stable, they do in some ways lack in support for very large zones like that of a country code TLD.<!--more--><\/p>\n<p>While other registries started supporting live updates of their nameservers in the past years, DENIC for example couldn&#8217;t offer this service, since they had to actually disable one of their nameservers, load the new information for the complete .de-zone, make that nameserver available again and then do the same thing for the next nameserver. While this normally didn&#8217;t cause any downtime, because of the load-balanced way the nameservers where set-up, this can cause problems. Like we have seen today when the new zonefile turned out to be completely empty.<\/p>\n<p>An official statement of DENIC about what happened earlier today, hasn&#8217;t been made available. But it looks like they started loading in new zonefiles automatically, having to notice too late that the new zonefile actually didn&#8217;t contain any information (or only contained a small portion of the information that should have been in there) and that they had therefore technically deleted all .de domain names.<\/p>\n<p>Do note that, if you have e-mail accounts ending in a .de domain name, that mails sent to you while the .de zone was done will not arrive. Contrary to when a mailserver is down, the mailserver trying to send you an e-mail will not try to make a second attempt if the nameservers are down, as was the case today.<\/p>\n<p>Also domain names under other extensions using nameservers exclusively under .de will have been unreachable during the downtime of the .de-registry<\/p>\n<p>This once again stresses how important it is to have a good and robust nameserver infrastructure. Our website recently started using nameservers under five different TLD&#8217;s, just in case something happens like we have seen today.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>From 13:30 through about 14:50 today, large parts of the .de zone where unavailable, causing most if not all of the 13 million .de domain names with websites and e-mail to be unavailable. It is very uncommon for a large domain name extension to be fully unavailable, so much that it is causing domain names [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts\/640"}],"collection":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/comments?post=640"}],"version-history":[{"count":10,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts\/640\/revisions"}],"predecessor-version":[{"id":2083,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts\/640\/revisions\/2083"}],"wp:attachment":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/media?parent=640"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/categories?post=640"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/tags?post=640"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}