Home / News I have a News Tip

Misconfiguration Brings Down Entire .SE Domain in Sweden

A incorrect configuration within Swedens .SE zone caused temporary shutdown of all websites under the country code top-level domain. Web monitoring company, Royal Pingdom, also located in Sweden reports: "Last night, a routine maintenance of Sweden's top-level domain .se went seriously wrong, introducing an error that made DNS lookups for all .se domain names start failing. The entire Swedish Internet effectively stopped working at this point. Swedish (.se) websites could not be reached, email to Swedish domain names stopped working, and for many these problems persist still. According to sources we have inside the Swedish web hosting industry, the .se zone, the central record for the .se top-level domain, broke at 21:45 local time and was not returned to normal until 22:43 local time."

Follow CircleID on

If you are pressed for time ...

... this is for you. More and more professionals are choosing to publish critical posts on CircleID from all corners of the Internet industry. If you find it hard to keep up daily, consider subscribing to our weekly digest. We will provide you a convenient summary report once a week sent directly to your inbox. It's a quick and easy read.

I make a point of reading CircleID. There is no getting around the utility of knowing what thoughtful people are thinking and saying about our industry.

Vinton Cerf, Co-designer of the TCP/IP Protocols & the Architecture of the Internet

Share your comments

DNS Early Warning System Karl Auerbach  –  Oct 13, 2009 10:17 AM PST

On my very first day on the ICANN board of directors in 2000 I recommended that ICANN establish an "early warning system" to watch root and top level domain behaviour for signs of errors or instability.

It would have been a relatively lightweight system of simple scripts that did queries and applied heuristics to look for patterns suggesting problems.  There was potential buy-in from a company that already had a worldwide array of machines that monitor website activity - in other words ICANN would could have gotten a free ride on an existing infrastructure.

I believe that such a system could have quickly detected the .se error before it had time to propagate widely into DNS caches.

ICANN's response at the time, and ever since, has been to yawn, as if to say, "we don't care about real DNS stability, we care only about trademarks."

To post comments, please login or create an account.




Sponsored byThreat Intelligence Platform

DNS Security

Sponsored byAfilias

IP Addressing

Sponsored byAvenue4 LLC

Domain Names

Sponsored byVerisign

Brand Protection

Sponsored byAppDetex

New TLDs

Sponsored byAfilias


Sponsored byWhoisXML API


Sponsored byVerisign