<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_10_13_1537207</id>
	<title>Entire<nobr> <wbr></nobr>.SE TLD Drops Off the Internet</title>
	<author>timothy</author>
	<datestamp>1255449660000</datestamp>
	<htmltext>Icemaann writes <i>"Pingdom and Network World are reporting that the  SE tld <a href="http://royal.pingdom.com/2009/10/13/sweden\%25E2\%2580\%2599s-internet-broken-by-dns-mistake/">dropped off the internet yesterday</a> due to a <a href="http://www.networkworld.com/community/node/46115">bug in the script that generates the SE zone file</a>. The SE tld has close to one million domains that all went down due to missing the trailing dot in the SE zone file. Some caching nameservers may still be returning invalid DNS responses for 24 hours."</i></htmltext>
<tokenext>Icemaann writes " Pingdom and Network World are reporting that the SE tld dropped off the internet yesterday due to a bug in the script that generates the SE zone file .
The SE tld has close to one million domains that all went down due to missing the trailing dot in the SE zone file .
Some caching nameservers may still be returning invalid DNS responses for 24 hours .
"</tokentext>
<sentencetext>Icemaann writes "Pingdom and Network World are reporting that the  SE tld dropped off the internet yesterday due to a bug in the script that generates the SE zone file.
The SE tld has close to one million domains that all went down due to missing the trailing dot in the SE zone file.
Some caching nameservers may still be returning invalid DNS responses for 24 hours.
"</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29746277</id>
	<title>movie and music industry</title>
	<author>cre\_slash</author>
	<datestamp>1255541400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>so this is not something done by MPAA or RIAA to prevent people from accessing thepiratebay?<nobr> <wbr></nobr>:P</htmltext>
<tokenext>so this is not something done by MPAA or RIAA to prevent people from accessing thepiratebay ?
: P</tokentext>
<sentencetext>so this is not something done by MPAA or RIAA to prevent people from accessing thepiratebay?
:P</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734495</id>
	<title>Re:DNS is the problem</title>
	<author>Anonymous</author>
	<datestamp>1255460400000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>It still boggles my mind that anyone thought zone files are a good idea.  The file format is so damn brittle, that a single byte can spell disaster.</p></div><p>What's a zonefile? I use Dynamic Update for all my DNS maintenance, you insensitive clod!</p></div>
	</htmltext>
<tokenext>It still boggles my mind that anyone thought zone files are a good idea .
The file format is so damn brittle , that a single byte can spell disaster.What 's a zonefile ?
I use Dynamic Update for all my DNS maintenance , you insensitive clod !</tokentext>
<sentencetext>It still boggles my mind that anyone thought zone files are a good idea.
The file format is so damn brittle, that a single byte can spell disaster.What's a zonefile?
I use Dynamic Update for all my DNS maintenance, you insensitive clod!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29739823</id>
	<title>internet?</title>
	<author>Anonymous</author>
	<datestamp>1255443120000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>what's that?<br>XD</p></htmltext>
<tokenext>what 's that ? XD</tokentext>
<sentencetext>what's that?XD</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29742967</id>
	<title>Whay should somebody be fired for this?</title>
	<author>jotaeleemeese</author>
	<datestamp>1255524960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I am sick and tired of this kind of knee jerk reaction.</p><p>Unless is somebody that consistently has been messing things up and has been warned, I don't see why this should be a firing somebody issue.</p><p>It is not like we are all perfect, right?. RIGHT?</p></htmltext>
<tokenext>I am sick and tired of this kind of knee jerk reaction.Unless is somebody that consistently has been messing things up and has been warned , I do n't see why this should be a firing somebody issue.It is not like we are all perfect , right ? .
RIGHT ?</tokentext>
<sentencetext>I am sick and tired of this kind of knee jerk reaction.Unless is somebody that consistently has been messing things up and has been warned, I don't see why this should be a firing somebody issue.It is not like we are all perfect, right?.
RIGHT?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29739611</id>
	<title>Simple solution</title>
	<author>straponego</author>
	<datestamp>1255441680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Everybody set all your TTLs to 1.</htmltext>
<tokenext>Everybody set all your TTLs to 1 .</tokentext>
<sentencetext>Everybody set all your TTLs to 1.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734611</id>
	<title>Re:unless you are swedish</title>
	<author>camperdave</author>
	<datestamp>1255460880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><i>If a packet gets through, great. If not, well, it's not the end of the world.</i> <br> <br>
Tell that to the "Operation SpoilSport" computers running the missle silos.</htmltext>
<tokenext>If a packet gets through , great .
If not , well , it 's not the end of the world .
Tell that to the " Operation SpoilSport " computers running the missle silos .</tokentext>
<sentencetext>If a packet gets through, great.
If not, well, it's not the end of the world.
Tell that to the "Operation SpoilSport" computers running the missle silos.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733277</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29739789</id>
	<title>Re:No big deal</title>
	<author>tdknox</author>
	<datestamp>1255442880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Speaking as someone who has done root DNS modifications, Sweden *doesn't do* the modifications. They submit a request, which is verified by two separate agencies, then forwarded on to VeriSign who makes the TLD change. Once the change is made, it is (supposedly) verified by at least 1 other person, and several scripts before being pushed live.</p></htmltext>
<tokenext>Speaking as someone who has done root DNS modifications , Sweden * does n't do * the modifications .
They submit a request , which is verified by two separate agencies , then forwarded on to VeriSign who makes the TLD change .
Once the change is made , it is ( supposedly ) verified by at least 1 other person , and several scripts before being pushed live .</tokentext>
<sentencetext>Speaking as someone who has done root DNS modifications, Sweden *doesn't do* the modifications.
They submit a request, which is verified by two separate agencies, then forwarded on to VeriSign who makes the TLD change.
Once the change is made, it is (supposedly) verified by at least 1 other person, and several scripts before being pushed live.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733111</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733179</id>
	<title>unless you are swedish</title>
	<author>circletimessquare</author>
	<datestamp>1255454820000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>i don't think you have a right to call this no big deal</p><p>the internet is becoming more and more vital to our lives</p><p>its "no big deal" until you need to know something off the internet right now, high stakes</p></htmltext>
<tokenext>i do n't think you have a right to call this no big dealthe internet is becoming more and more vital to our livesits " no big deal " until you need to know something off the internet right now , high stakes</tokentext>
<sentencetext>i don't think you have a right to call this no big dealthe internet is becoming more and more vital to our livesits "no big deal" until you need to know something off the internet right now, high stakes</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733417</id>
	<title>Re:No big deal</title>
	<author>CorporateSuit</author>
	<datestamp>1255455900000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p><div class="quote"><p>The downtime lasted 30 minutes, and most domains were probably cached by nameservers anyway.</p></div><p>I didn't notice the DNS freak out, but I did notice the internet's smug meter had dropped about 30\%.</p></div>
	</htmltext>
<tokenext>The downtime lasted 30 minutes , and most domains were probably cached by nameservers anyway.I did n't notice the DNS freak out , but I did notice the internet 's smug meter had dropped about 30 \ % .</tokentext>
<sentencetext>The downtime lasted 30 minutes, and most domains were probably cached by nameservers anyway.I didn't notice the DNS freak out, but I did notice the internet's smug meter had dropped about 30\%.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733277</id>
	<title>Re:unless you are swedish</title>
	<author>Hyppy</author>
	<datestamp>1255455300000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext>The Internet was started as, and always has been, a "best effort" network.  If a packet gets through, great.  If not, well, it's not the end of the world.  People have tried to code more and more resilient protocols on top to be as robust as possible, but in the end it's a very fragile system that can go down quite easily.
<br> <br>
Anything sufficiently "high stakes" shouldn't rely on an unreliable medium.</htmltext>
<tokenext>The Internet was started as , and always has been , a " best effort " network .
If a packet gets through , great .
If not , well , it 's not the end of the world .
People have tried to code more and more resilient protocols on top to be as robust as possible , but in the end it 's a very fragile system that can go down quite easily .
Anything sufficiently " high stakes " should n't rely on an unreliable medium .</tokentext>
<sentencetext>The Internet was started as, and always has been, a "best effort" network.
If a packet gets through, great.
If not, well, it's not the end of the world.
People have tried to code more and more resilient protocols on top to be as robust as possible, but in the end it's a very fragile system that can go down quite easily.
Anything sufficiently "high stakes" shouldn't rely on an unreliable medium.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733179</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733561</id>
	<title>Re:No big deal</title>
	<author>Anonymous</author>
	<datestamp>1255456500000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext>The actual downtime is no big deal, but the reason it happened is.  Evidently, the registrar for an entire country's domain likes to roll out changes to the primary zone file without any sort of testing or syntax checking first.  Simply having a small network (one or two computers) running a test root server, and running your scripts against that first, would have discovered the bug.
<br> <br>
DNS is very simple, but it's just as prone to human error as anything else.  If you're responsible for the records of a large number of domains (like, say, an entire country), you probably ought to take some time to develop proper testing and change control procedures before you fiddle with it.  It sounds like these guys didn't take it seriously enough and got burned.  I hope they'll learn their lesson from this and change their procedures.</htmltext>
<tokenext>The actual downtime is no big deal , but the reason it happened is .
Evidently , the registrar for an entire country 's domain likes to roll out changes to the primary zone file without any sort of testing or syntax checking first .
Simply having a small network ( one or two computers ) running a test root server , and running your scripts against that first , would have discovered the bug .
DNS is very simple , but it 's just as prone to human error as anything else .
If you 're responsible for the records of a large number of domains ( like , say , an entire country ) , you probably ought to take some time to develop proper testing and change control procedures before you fiddle with it .
It sounds like these guys did n't take it seriously enough and got burned .
I hope they 'll learn their lesson from this and change their procedures .</tokentext>
<sentencetext>The actual downtime is no big deal, but the reason it happened is.
Evidently, the registrar for an entire country's domain likes to roll out changes to the primary zone file without any sort of testing or syntax checking first.
Simply having a small network (one or two computers) running a test root server, and running your scripts against that first, would have discovered the bug.
DNS is very simple, but it's just as prone to human error as anything else.
If you're responsible for the records of a large number of domains (like, say, an entire country), you probably ought to take some time to develop proper testing and change control procedures before you fiddle with it.
It sounds like these guys didn't take it seriously enough and got burned.
I hope they'll learn their lesson from this and change their procedures.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733361</id>
	<title>Re:TPB</title>
	<author>Anonymous</author>
	<datestamp>1255455600000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I was going to riff on that but you beat me to it. But I would have said:</p><p><b>Apparently the *aa's are also too stupid to realize that just because The Pirate Bay admins are Swedish, it doesn't mean that TPB has a<nobr> <wbr></nobr>.se tld.</b></p><p>That way, it would have been funny.</p></htmltext>
<tokenext>I was going to riff on that but you beat me to it .
But I would have said : Apparently the * aa 's are also too stupid to realize that just because The Pirate Bay admins are Swedish , it does n't mean that TPB has a .se tld.That way , it would have been funny .</tokentext>
<sentencetext>I was going to riff on that but you beat me to it.
But I would have said:Apparently the *aa's are also too stupid to realize that just because The Pirate Bay admins are Swedish, it doesn't mean that TPB has a .se tld.That way, it would have been funny.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732877</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29738171</id>
	<title>Re:Why MaraDNS uses a special zone file format</title>
	<author>Anonymous</author>
	<datestamp>1255432380000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>For people who want to use their BIND zonefiles, there is included a Python script that converts a BIND zonefile in to MaraDNS' similar zone file format.</p></div><p>Oh man, another step for me to perform when updating one of my zones? Let's automate that last one through a script!</p></div>
	</htmltext>
<tokenext>For people who want to use their BIND zonefiles , there is included a Python script that converts a BIND zonefile in to MaraDNS ' similar zone file format.Oh man , another step for me to perform when updating one of my zones ?
Let 's automate that last one through a script !</tokentext>
<sentencetext>For people who want to use their BIND zonefiles, there is included a Python script that converts a BIND zonefile in to MaraDNS' similar zone file format.Oh man, another step for me to perform when updating one of my zones?
Let's automate that last one through a script!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733733</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734775</id>
	<title>Re:No big deal</title>
	<author>mcgrew</author>
	<datestamp>1255461660000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>I wish browsers would store the IP address of the page as well as the domain name in bookmarks. That way if the DNS server goes down you could still get to the site. Of course, the primary lookup should still be the domain name, since a site can have its address changed; the browser would only look at the IP if the DNS lookup failed.</p></htmltext>
<tokenext>I wish browsers would store the IP address of the page as well as the domain name in bookmarks .
That way if the DNS server goes down you could still get to the site .
Of course , the primary lookup should still be the domain name , since a site can have its address changed ; the browser would only look at the IP if the DNS lookup failed .</tokentext>
<sentencetext>I wish browsers would store the IP address of the page as well as the domain name in bookmarks.
That way if the DNS server goes down you could still get to the site.
Of course, the primary lookup should still be the domain name, since a site can have its address changed; the browser would only look at the IP if the DNS lookup failed.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29737389</id>
	<title>Re:No big deal</title>
	<author>Anonymous</author>
	<datestamp>1255429200000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>This happened in Sweden - of course.</p><p>I'm sure the change was made at like 4:45 PM (or 16:45 if you prefer) and you know...the day was over<nobr> <wbr></nobr>...and if he'd been late getting home he'd have heard about it.</p><p>Happens all the time.</p></htmltext>
<tokenext>This happened in Sweden - of course.I 'm sure the change was made at like 4 : 45 PM ( or 16 : 45 if you prefer ) and you know...the day was over ...and if he 'd been late getting home he 'd have heard about it.Happens all the time .</tokentext>
<sentencetext>This happened in Sweden - of course.I'm sure the change was made at like 4:45 PM (or 16:45 if you prefer) and you know...the day was over ...and if he'd been late getting home he'd have heard about it.Happens all the time.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733561</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733201</id>
	<title>Re:So I guess it's...</title>
	<author>vandelais</author>
	<datestamp>1255454880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'm chopping up the zone files if that's ok with you (tosses random shyte over shoulder)<br>We'll scoop up all the trailing dots and put them in the stew</p><p>BORKBORKBORK!</p></htmltext>
<tokenext>I 'm chopping up the zone files if that 's ok with you ( tosses random shyte over shoulder ) We 'll scoop up all the trailing dots and put them in the stewBORKBORKBORK !</tokentext>
<sentencetext>I'm chopping up the zone files if that's ok with you (tosses random shyte over shoulder)We'll scoop up all the trailing dots and put them in the stewBORKBORKBORK!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733093</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733351</id>
	<title>Re:unless you are swedish</title>
	<author>clemdoc</author>
	<datestamp>1255455600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>In which case you should have been thinking about taking your own precautions.</htmltext>
<tokenext>In which case you should have been thinking about taking your own precautions .</tokentext>
<sentencetext>In which case you should have been thinking about taking your own precautions.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733179</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733477</id>
	<title>so..</title>
	<author>PPNSteve</author>
	<datestamp>1255456320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>the trailing dot got<nobr> <wbr></nobr>/.'d?</htmltext>
<tokenext>the trailing dot got / .
'd ?</tokentext>
<sentencetext>the trailing dot got /.
'd?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734765</id>
	<title>Re:There goes my favorite web site ! [Goat...]</title>
	<author>Tablizer</author>
	<datestamp>1255461600000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>Don't worry, there's plenty of mirrors......unfortunately.</p></htmltext>
<tokenext>Do n't worry , there 's plenty of mirrors......unfortunately .</tokentext>
<sentencetext>Don't worry, there's plenty of mirrors......unfortunately.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732903</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895</id>
	<title>No big deal</title>
	<author>Anonymous</author>
	<datestamp>1255453440000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>The downtime lasted 30 minutes, and most domains were probably cached by nameservers anyway.</p></htmltext>
<tokenext>The downtime lasted 30 minutes , and most domains were probably cached by nameservers anyway .</tokentext>
<sentencetext>The downtime lasted 30 minutes, and most domains were probably cached by nameservers anyway.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734825</id>
	<title>Re:TPB</title>
	<author>Anonymous</author>
	<datestamp>1255461780000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><p>It looks like someone messed up the summary.  I'm pretty sure it should be:</p><p><div class="quote"><p>Peengdum und Netvurk Vurld ere-a repurteeng thet zee SE tld drupped ooffff zee internet yesterdey dooe-a tu a boog in zee screept thet generetes zee SE zune-a feele-a. Zee SE tld hes cluse-a tu oone-a meelliun dumeeens thet ell vent doon dooe-a tu meessing zee treeeling dut in zee SE zune-a feele-a. Sume-a cecheeng nemeserfers mey steell be-a retoorneeng infeleed DNS respunses fur 24 huoors.</p></div></div>
	</htmltext>
<tokenext>It looks like someone messed up the summary .
I 'm pretty sure it should be : Peengdum und Netvurk Vurld ere-a repurteeng thet zee SE tld drupped ooffff zee internet yesterdey dooe-a tu a boog in zee screept thet generetes zee SE zune-a feele-a .
Zee SE tld hes cluse-a tu oone-a meelliun dumeeens thet ell vent doon dooe-a tu meessing zee treeeling dut in zee SE zune-a feele-a .
Sume-a cecheeng nemeserfers mey steell be-a retoorneeng infeleed DNS respunses fur 24 huoors .</tokentext>
<sentencetext>It looks like someone messed up the summary.
I'm pretty sure it should be:Peengdum und Netvurk Vurld ere-a repurteeng thet zee SE tld drupped ooffff zee internet yesterdey dooe-a tu a boog in zee screept thet generetes zee SE zune-a feele-a.
Zee SE tld hes cluse-a tu oone-a meelliun dumeeens thet ell vent doon dooe-a tu meessing zee treeeling dut in zee SE zune-a feele-a.
Sume-a cecheeng nemeserfers mey steell be-a retoorneeng infeleed DNS respunses fur 24 huoors.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732877</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733467</id>
	<title>Re:change control / management, anyone?</title>
	<author>Anonymous</author>
	<datestamp>1255456200000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext><p><div class="quote"><p>I seriously hope someone is fired or loses a contract over this.</p></div><p>You'll be happy to know that the person responsible have been found. The person in question was described as having unusual bushy eyebrows and speaking in a thick Swedish accent. His last comment about the incident, before being dragged away, was "bork bork bork".</p></div>
	</htmltext>
<tokenext>I seriously hope someone is fired or loses a contract over this.You 'll be happy to know that the person responsible have been found .
The person in question was described as having unusual bushy eyebrows and speaking in a thick Swedish accent .
His last comment about the incident , before being dragged away , was " bork bork bork " .</tokentext>
<sentencetext>I seriously hope someone is fired or loses a contract over this.You'll be happy to know that the person responsible have been found.
The person in question was described as having unusual bushy eyebrows and speaking in a thick Swedish accent.
His last comment about the incident, before being dragged away, was "bork bork bork".
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735425</id>
	<title>Re:change control / management, anyone?</title>
	<author>kirillian</author>
	<datestamp>1255464840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>F*** You! I <b>right</b> code</p></div><p><div class="quote"><p>we <b>right</b> the requirement down</p></div><p>I think I found the reason why you keep getting those airplane system parts back (right -&gt; write)</p><p>Seriously though, I think you just forgot your<nobr> <wbr></nobr>/sarcasm tag...</p><p>My dad repairs airplane systems as well...he works with diagnosing/repairing/redesigning those circuit boards on the fly...they come in, like you said, late in the week, with that Friday deadline...then again...my boss likes to call up 5 minutes before go time, and ask me, "Can you just change this for me right quick?" That wouldn't bother me so much if people realized that something like that just ASKS for errors and bugs, especially the more complicated something is...No matter how careful the programmer and no matter how many unit tests you have, trying to code something in five minutes just is a bad habit to be in...it doesn't give you the time to think about various extreme cases and scenarios that could crop up.</p></div>
	</htmltext>
<tokenext>F * * * You !
I right codewe right the requirement downI think I found the reason why you keep getting those airplane system parts back ( right - &gt; write ) Seriously though , I think you just forgot your /sarcasm tag...My dad repairs airplane systems as well...he works with diagnosing/repairing/redesigning those circuit boards on the fly...they come in , like you said , late in the week , with that Friday deadline...then again...my boss likes to call up 5 minutes before go time , and ask me , " Can you just change this for me right quick ?
" That would n't bother me so much if people realized that something like that just ASKS for errors and bugs , especially the more complicated something is...No matter how careful the programmer and no matter how many unit tests you have , trying to code something in five minutes just is a bad habit to be in...it does n't give you the time to think about various extreme cases and scenarios that could crop up .</tokentext>
<sentencetext>F*** You!
I right codewe right the requirement downI think I found the reason why you keep getting those airplane system parts back (right -&gt; write)Seriously though, I think you just forgot your /sarcasm tag...My dad repairs airplane systems as well...he works with diagnosing/repairing/redesigning those circuit boards on the fly...they come in, like you said, late in the week, with that Friday deadline...then again...my boss likes to call up 5 minutes before go time, and ask me, "Can you just change this for me right quick?
" That wouldn't bother me so much if people realized that something like that just ASKS for errors and bugs, especially the more complicated something is...No matter how careful the programmer and no matter how many unit tests you have, trying to code something in five minutes just is a bad habit to be in...it doesn't give you the time to think about various extreme cases and scenarios that could crop up.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733311</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732903</id>
	<title>There goes my favorite web site !</title>
	<author>Anonymous</author>
	<datestamp>1255453440000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext><p>Goat.se</p></htmltext>
<tokenext>Goat.se</tokentext>
<sentencetext>Goat.se</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733003</id>
	<title>An oft overlooked single point of failure?</title>
	<author>Anonymous</author>
	<datestamp>1255453920000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Wouldn't it be better if you could have 2 totally independent firms managing each top-level domain name?   Sure it'd be some work to make sure updates get to each of them; but it might protect against things like this.</p></htmltext>
<tokenext>Would n't it be better if you could have 2 totally independent firms managing each top-level domain name ?
Sure it 'd be some work to make sure updates get to each of them ; but it might protect against things like this .</tokentext>
<sentencetext>Wouldn't it be better if you could have 2 totally independent firms managing each top-level domain name?
Sure it'd be some work to make sure updates get to each of them; but it might protect against things like this.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734133</id>
	<title>Re:DNS is the problem</title>
	<author>bwalling</author>
	<datestamp>1255458960000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext>You do recognize that most of the protocols and specifications running the Internet are decades old, right?  The fact that they've lasted this long is really rather impressive.<br> <br>Besides, if we redesigned it now, it would be insanely complex and bloated, not to mention never fully implemented (CSS? ha!), as there would be too many parties "contributing".</htmltext>
<tokenext>You do recognize that most of the protocols and specifications running the Internet are decades old , right ?
The fact that they 've lasted this long is really rather impressive .
Besides , if we redesigned it now , it would be insanely complex and bloated , not to mention never fully implemented ( CSS ?
ha ! ) , as there would be too many parties " contributing " .</tokentext>
<sentencetext>You do recognize that most of the protocols and specifications running the Internet are decades old, right?
The fact that they've lasted this long is really rather impressive.
Besides, if we redesigned it now, it would be insanely complex and bloated, not to mention never fully implemented (CSS?
ha!), as there would be too many parties "contributing".</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733733</id>
	<title>Why MaraDNS uses a special zone file format</title>
	<author>MaraDNS</author>
	<datestamp>1255457400000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>
This is why <a href="http://maradns.org/" title="maradns.org" rel="nofollow">MaraDNS</a> [maradns.org] (my open-source DNS server) uses a special zone file format.
</p><p>
MaraDNS uses a zone file format that, for the most part, resembles BIND zone files.  However, the zone file format has some minor differences so the common "Forgot to put a dot at the end of a hostname" and the "forgot to update the SOA serial number" problems do not happen; a domain name without a dot at the end in a syntax error in MaraDNS' zone file parser; if you want to end a hostname with the name of the zone in question, this has to be explicitly specified with a<nobr> <wbr></nobr><tt>.\%</tt> at the end of the hostname.
</p><p>
There is also a mechanism for automatically generating SOA records, or having a SOA record where the serial is automatically updated based on the "last write" timestamp for the zone file.
</p><p>
For people who want to use their BIND zonefiles, there is included a Python script that converts a BIND zonefile in to MaraDNS' similar zone file format.</p></htmltext>
<tokenext>This is why MaraDNS [ maradns.org ] ( my open-source DNS server ) uses a special zone file format .
MaraDNS uses a zone file format that , for the most part , resembles BIND zone files .
However , the zone file format has some minor differences so the common " Forgot to put a dot at the end of a hostname " and the " forgot to update the SOA serial number " problems do not happen ; a domain name without a dot at the end in a syntax error in MaraDNS ' zone file parser ; if you want to end a hostname with the name of the zone in question , this has to be explicitly specified with a . \ % at the end of the hostname .
There is also a mechanism for automatically generating SOA records , or having a SOA record where the serial is automatically updated based on the " last write " timestamp for the zone file .
For people who want to use their BIND zonefiles , there is included a Python script that converts a BIND zonefile in to MaraDNS ' similar zone file format .</tokentext>
<sentencetext>
This is why MaraDNS [maradns.org] (my open-source DNS server) uses a special zone file format.
MaraDNS uses a zone file format that, for the most part, resembles BIND zone files.
However, the zone file format has some minor differences so the common "Forgot to put a dot at the end of a hostname" and the "forgot to update the SOA serial number" problems do not happen; a domain name without a dot at the end in a syntax error in MaraDNS' zone file parser; if you want to end a hostname with the name of the zone in question, this has to be explicitly specified with a .\% at the end of the hostname.
There is also a mechanism for automatically generating SOA records, or having a SOA record where the serial is automatically updated based on the "last write" timestamp for the zone file.
For people who want to use their BIND zonefiles, there is included a Python script that converts a BIND zonefile in to MaraDNS' similar zone file format.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29738111</id>
	<title>Re:No big deal</title>
	<author>zapakh</author>
	<datestamp>1255432020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I once viddied an animated documentary about <a href="http://en.wikipedia.org/wiki/Over\_Logging" title="wikipedia.org" rel="nofollow">a small town in Colorado that lost the internet for 22 minutes</a> [wikipedia.org].  It was not pretty.  Our hearts and minds go out to you, people of Sweden.  I cannot even fathom what that would be like<nobr> <wbr></nobr>... I hope the looting and rioting has died down with the restoration of the internet.</p></div><p>At least it wasn't <a href="http://en.wikipedia.org/wiki/Pinewood\_Derby\_(South\_Park)" title="wikipedia.org" rel="nofollow">Finland</a> [wikipedia.org].
</p><p>
All the same, somebody better tell Norway.  They were really close.</p></div>
	</htmltext>
<tokenext>I once viddied an animated documentary about a small town in Colorado that lost the internet for 22 minutes [ wikipedia.org ] .
It was not pretty .
Our hearts and minds go out to you , people of Sweden .
I can not even fathom what that would be like ... I hope the looting and rioting has died down with the restoration of the internet.At least it was n't Finland [ wikipedia.org ] .
All the same , somebody better tell Norway .
They were really close .</tokentext>
<sentencetext>I once viddied an animated documentary about a small town in Colorado that lost the internet for 22 minutes [wikipedia.org].
It was not pretty.
Our hearts and minds go out to you, people of Sweden.
I cannot even fathom what that would be like ... I hope the looting and rioting has died down with the restoration of the internet.At least it wasn't Finland [wikipedia.org].
All the same, somebody better tell Norway.
They were really close.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733709</id>
	<title>Re:change control / management, anyone?</title>
	<author>cjeze</author>
	<datestamp>1255457280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>To Err Is Human, To Forgive Divine.<br> <br>


Even with validation, change control etc errors can occur. Even with the most rigorous testing errors can happen, just look at NASA they are rocket scientists and even they make mistakes every now and then. Next time it could be you.</htmltext>
<tokenext>To Err Is Human , To Forgive Divine .
Even with validation , change control etc errors can occur .
Even with the most rigorous testing errors can happen , just look at NASA they are rocket scientists and even they make mistakes every now and then .
Next time it could be you .</tokentext>
<sentencetext>To Err Is Human, To Forgive Divine.
Even with validation, change control etc errors can occur.
Even with the most rigorous testing errors can happen, just look at NASA they are rocket scientists and even they make mistakes every now and then.
Next time it could be you.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733597</id>
	<title>Re:change control / management, anyone?</title>
	<author>Anonymous</author>
	<datestamp>1255456740000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>In my experience, excessive paperwork makes such things <i>more</i> likely, not less.</p><p>"Change control" in particular.  PHBs don't make good programmers, and only PHBs think "change control" means more than "testing your code".</p></htmltext>
<tokenext>In my experience , excessive paperwork makes such things more likely , not less .
" Change control " in particular .
PHBs do n't make good programmers , and only PHBs think " change control " means more than " testing your code " .</tokentext>
<sentencetext>In my experience, excessive paperwork makes such things more likely, not less.
"Change control" in particular.
PHBs don't make good programmers, and only PHBs think "change control" means more than "testing your code".</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733111</id>
	<title>Re:No big deal</title>
	<author>Anonymous</author>
	<datestamp>1255454520000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>While the <i>impact</i> of this is no big deal, it's still kind of scary that the people running a decently-sized ccTLD would make such a novice mistake on their zonefile.</p></htmltext>
<tokenext>While the impact of this is no big deal , it 's still kind of scary that the people running a decently-sized ccTLD would make such a novice mistake on their zonefile .</tokentext>
<sentencetext>While the impact of this is no big deal, it's still kind of scary that the people running a decently-sized ccTLD would make such a novice mistake on their zonefile.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29736007</id>
	<title>Re:change control / management, anyone?</title>
	<author>Blakey Rat</author>
	<datestamp>1255467300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><i>at 2am, I, and most mammals, are not at their mental best,</i></p><p>I'm a black-footed ferret, you insensitive clod!</p></htmltext>
<tokenext>at 2am , I , and most mammals , are not at their mental best,I 'm a black-footed ferret , you insensitive clod !</tokentext>
<sentencetext>at 2am, I, and most mammals, are not at their mental best,I'm a black-footed ferret, you insensitive clod!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735023</id>
	<title>Re:No big deal</title>
	<author>Anonymous</author>
	<datestamp>1255462980000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Don't you mean a TLD server, and not a root server? I suppose you could have one test server that claimed to be authoritative for both the root and the TLD. I would personally, run a test root server with a modified entry for "se.", that points to the test TLD server. I would then run my test resolving DNS server with a configuration that treats my test root server as the sole real root server. There is no need to run test 2ld servers since the reals ones work fine. Just have the client look up a bunch of different adresses, of a large variety of types, including some outside the se tld, to make sure everything works.</p><p>That is a few more than two machines, but could still be run in VMs on a single low end server without too much difficulty. This would only protect against some very specific types of problems, and not ones such as a change in the zone file requires more processing for each lookup for some reason, which could cause problems with load, but it catches problems where the zone file formatting is invalid, and whatnot.</p></htmltext>
<tokenext>Do n't you mean a TLD server , and not a root server ?
I suppose you could have one test server that claimed to be authoritative for both the root and the TLD .
I would personally , run a test root server with a modified entry for " se .
" , that points to the test TLD server .
I would then run my test resolving DNS server with a configuration that treats my test root server as the sole real root server .
There is no need to run test 2ld servers since the reals ones work fine .
Just have the client look up a bunch of different adresses , of a large variety of types , including some outside the se tld , to make sure everything works.That is a few more than two machines , but could still be run in VMs on a single low end server without too much difficulty .
This would only protect against some very specific types of problems , and not ones such as a change in the zone file requires more processing for each lookup for some reason , which could cause problems with load , but it catches problems where the zone file formatting is invalid , and whatnot .</tokentext>
<sentencetext>Don't you mean a TLD server, and not a root server?
I suppose you could have one test server that claimed to be authoritative for both the root and the TLD.
I would personally, run a test root server with a modified entry for "se.
", that points to the test TLD server.
I would then run my test resolving DNS server with a configuration that treats my test root server as the sole real root server.
There is no need to run test 2ld servers since the reals ones work fine.
Just have the client look up a bunch of different adresses, of a large variety of types, including some outside the se tld, to make sure everything works.That is a few more than two machines, but could still be run in VMs on a single low end server without too much difficulty.
This would only protect against some very specific types of problems, and not ones such as a change in the zone file requires more processing for each lookup for some reason, which could cause problems with load, but it catches problems where the zone file formatting is invalid, and whatnot.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733561</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733791</id>
	<title>NSD</title>
	<author>funkboy</author>
	<datestamp>1255457520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If they were using <a href="http://www.nlnetlabs.nl/projects/nsd/" title="nlnetlabs.nl" rel="nofollow">NSD</a> [nlnetlabs.nl] like the RIPE does for <a href="http://k.root-servers.org/" title="root-servers.org" rel="nofollow">K root</a> [root-servers.org], the zone compiler wouldn't have compiled the faulty zone file and the parser would have made noise about it.  NSD is very hard to break as the zone files must be compiled into a database before loading. The parser simply refuses to compile when there are zones with errors in them, so the database it creates will never be bogus (similar to the way a compiler won't create an executable if the source code violates its rules).</p></htmltext>
<tokenext>If they were using NSD [ nlnetlabs.nl ] like the RIPE does for K root [ root-servers.org ] , the zone compiler would n't have compiled the faulty zone file and the parser would have made noise about it .
NSD is very hard to break as the zone files must be compiled into a database before loading .
The parser simply refuses to compile when there are zones with errors in them , so the database it creates will never be bogus ( similar to the way a compiler wo n't create an executable if the source code violates its rules ) .</tokentext>
<sentencetext>If they were using NSD [nlnetlabs.nl] like the RIPE does for K root [root-servers.org], the zone compiler wouldn't have compiled the faulty zone file and the parser would have made noise about it.
NSD is very hard to break as the zone files must be compiled into a database before loading.
The parser simply refuses to compile when there are zones with errors in them, so the database it creates will never be bogus (similar to the way a compiler won't create an executable if the source code violates its rules).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735531</id>
	<title>Re:An oft overlooked single point of failure?</title>
	<author>jtcampbell</author>
	<datestamp>1255465380000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>What about regression testing?</p><p>It'd be quite possible to run a check and throw a warning if a change effects greater than a certain percentage of domains. Or you could check against a sample of domains that really aren't going to change (I'm thinking mcdonalds.se, ibm.se etc etc).</p></htmltext>
<tokenext>What about regression testing ? It 'd be quite possible to run a check and throw a warning if a change effects greater than a certain percentage of domains .
Or you could check against a sample of domains that really are n't going to change ( I 'm thinking mcdonalds.se , ibm.se etc etc ) .</tokentext>
<sentencetext>What about regression testing?It'd be quite possible to run a check and throw a warning if a change effects greater than a certain percentage of domains.
Or you could check against a sample of domains that really aren't going to change (I'm thinking mcdonalds.se, ibm.se etc etc).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733971</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733499</id>
	<title>More signs that the Idiocracy is fast approaching</title>
	<author>Eggplant62</author>
	<datestamp>1255456320000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Computers only do what the programmer tells them to do. Way to go, Sven, you fubared that script, eh?</p></htmltext>
<tokenext>Computers only do what the programmer tells them to do .
Way to go , Sven , you fubared that script , eh ?</tokentext>
<sentencetext>Computers only do what the programmer tells them to do.
Way to go, Sven, you fubared that script, eh?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735621</id>
	<title>Re:unless you are swedish</title>
	<author>an unsound mind</author>
	<datestamp>1255465680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>And if you need the internet so badly, just DNS going down shouldn't change much anything.</p></htmltext>
<tokenext>And if you need the internet so badly , just DNS going down should n't change much anything .</tokentext>
<sentencetext>And if you need the internet so badly, just DNS going down shouldn't change much anything.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733179</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735803</id>
	<title>Re:No big deal</title>
	<author>Anonymous</author>
	<datestamp>1255466460000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>The episode was actually set over several days</p></htmltext>
<tokenext>The episode was actually set over several days</tokentext>
<sentencetext>The episode was actually set over several days</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733999</id>
	<title>Re:DNS is the problem</title>
	<author>divisionbyzero</author>
	<datestamp>1255458420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>It still boggles my mind that anyone thought zone files are a good idea.  The file format is so damn brittle, that a single byte can spell disaster.  On top of that, the hierarchical naming structure presents an inherent systemic risk for all sub-domains as exhibited by this<nobr> <wbr></nobr>.se fiasco.  Nevermind the injection attacks, Pakistan taking out Youtube, and the rest, you have organizations like Verisign which profit immensely off of keeping the system broken.  And don't even bother mentioning DNSSEC, as it still doesn't resolve this fundamental issue.  The next systemic fuckup will simply be a signed fuckup.</p></div><p>Yes, it's a shame you were still in diapers when this solution was developed.  They could have benefited from your vast wisdom.  Or maybe not, if you think the problem with YouTube in Pakistan was due to DNS rather than BGP.</p></div>
	</htmltext>
<tokenext>It still boggles my mind that anyone thought zone files are a good idea .
The file format is so damn brittle , that a single byte can spell disaster .
On top of that , the hierarchical naming structure presents an inherent systemic risk for all sub-domains as exhibited by this .se fiasco .
Nevermind the injection attacks , Pakistan taking out Youtube , and the rest , you have organizations like Verisign which profit immensely off of keeping the system broken .
And do n't even bother mentioning DNSSEC , as it still does n't resolve this fundamental issue .
The next systemic fuckup will simply be a signed fuckup.Yes , it 's a shame you were still in diapers when this solution was developed .
They could have benefited from your vast wisdom .
Or maybe not , if you think the problem with YouTube in Pakistan was due to DNS rather than BGP .</tokentext>
<sentencetext>It still boggles my mind that anyone thought zone files are a good idea.
The file format is so damn brittle, that a single byte can spell disaster.
On top of that, the hierarchical naming structure presents an inherent systemic risk for all sub-domains as exhibited by this .se fiasco.
Nevermind the injection attacks, Pakistan taking out Youtube, and the rest, you have organizations like Verisign which profit immensely off of keeping the system broken.
And don't even bother mentioning DNSSEC, as it still doesn't resolve this fundamental issue.
The next systemic fuckup will simply be a signed fuckup.Yes, it's a shame you were still in diapers when this solution was developed.
They could have benefited from your vast wisdom.
Or maybe not, if you think the problem with YouTube in Pakistan was due to DNS rather than BGP.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733451</id>
	<title>Re:DNS is the problem</title>
	<author>RalphSleigh</author>
	<datestamp>1255456140000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>Pakistan taking out Youtube had absolutely nothing to do with DNS, they wrongly propagated a BGP announcement for the youtube IPs outside of Pakistan, so about 1/3 of the internet routed traffic into their black hole instead of to Youtube. Pretty effective blocking had they kept it internal, but they didn't.</p></htmltext>
<tokenext>Pakistan taking out Youtube had absolutely nothing to do with DNS , they wrongly propagated a BGP announcement for the youtube IPs outside of Pakistan , so about 1/3 of the internet routed traffic into their black hole instead of to Youtube .
Pretty effective blocking had they kept it internal , but they did n't .</tokentext>
<sentencetext>Pakistan taking out Youtube had absolutely nothing to do with DNS, they wrongly propagated a BGP announcement for the youtube IPs outside of Pakistan, so about 1/3 of the internet routed traffic into their black hole instead of to Youtube.
Pretty effective blocking had they kept it internal, but they didn't.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733601</id>
	<title>Minimally-Intrustive Cleanup (BIND-specific)</title>
	<author>Anonymous</author>
	<datestamp>1255456740000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>1. rndc dumpdb -all<br>2. grep some variant of "NS.*\.se\.se" out of the dump file<br>3. rndc flushname for each one</p><p>This works for relatively-small caches. In my case, only 40 flushnames were necessary. It might not be an option to do manually for big huge ISP caches, although it could be automated quite easily.</p></htmltext>
<tokenext>1. rndc dumpdb -all2 .
grep some variant of " NS .
* \ .se \ .se " out of the dump file3 .
rndc flushname for each oneThis works for relatively-small caches .
In my case , only 40 flushnames were necessary .
It might not be an option to do manually for big huge ISP caches , although it could be automated quite easily .</tokentext>
<sentencetext>1. rndc dumpdb -all2.
grep some variant of "NS.
*\.se\.se" out of the dump file3.
rndc flushname for each oneThis works for relatively-small caches.
In my case, only 40 flushnames were necessary.
It might not be an option to do manually for big huge ISP caches, although it could be automated quite easily.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734165</id>
	<title>Re:DNS is the problem</title>
	<author>photon317</author>
	<datestamp>1255459080000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>Part of the problem with DNS these days, which your post exemplifies, is that from very early on "BIND's implementation of DNS", and "DNS The Protocol" have been mashed together and confused by the RFC authors (who were involved with the BIND implementation and had motive to encourage the world to think only in BIND terms) and basically everyone who ever used DNS in any capacity.  Zonefiles are not implicit in DNS address resolution (neither for authoritative servers or recursive caches).  They really aren't any part of the wire DNS protocol for resolving names.  They *are* part of a wire protocol for secondary servers that slave zonefiles from primary servers, but even in that case it's really more a "BIND convention" than a necessity.  Ultimately how you transfer a zone's records from a master server to a slave server is up to however those two servers and their administrators agree to do so.  You can skip the AXFR protocol that uses zonefiles and instead do something else that works for both of you.  Inventing a new method of slaving zone data is easy and doesn't involved much complicated rollout.  Some people just rsync zonefiles for instance instead of using AXFR today.</p><p>It's really frustrating (believe me, I've done it) when you try to implement a new DNS server daemon from scratch from the RFCs, and you have to wade through this mess of "what's a BIND convention that doesn't matter and what's important to the actual DNS protocol for resolving names on the wire".</p></htmltext>
<tokenext>Part of the problem with DNS these days , which your post exemplifies , is that from very early on " BIND 's implementation of DNS " , and " DNS The Protocol " have been mashed together and confused by the RFC authors ( who were involved with the BIND implementation and had motive to encourage the world to think only in BIND terms ) and basically everyone who ever used DNS in any capacity .
Zonefiles are not implicit in DNS address resolution ( neither for authoritative servers or recursive caches ) .
They really are n't any part of the wire DNS protocol for resolving names .
They * are * part of a wire protocol for secondary servers that slave zonefiles from primary servers , but even in that case it 's really more a " BIND convention " than a necessity .
Ultimately how you transfer a zone 's records from a master server to a slave server is up to however those two servers and their administrators agree to do so .
You can skip the AXFR protocol that uses zonefiles and instead do something else that works for both of you .
Inventing a new method of slaving zone data is easy and does n't involved much complicated rollout .
Some people just rsync zonefiles for instance instead of using AXFR today.It 's really frustrating ( believe me , I 've done it ) when you try to implement a new DNS server daemon from scratch from the RFCs , and you have to wade through this mess of " what 's a BIND convention that does n't matter and what 's important to the actual DNS protocol for resolving names on the wire " .</tokentext>
<sentencetext>Part of the problem with DNS these days, which your post exemplifies, is that from very early on "BIND's implementation of DNS", and "DNS The Protocol" have been mashed together and confused by the RFC authors (who were involved with the BIND implementation and had motive to encourage the world to think only in BIND terms) and basically everyone who ever used DNS in any capacity.
Zonefiles are not implicit in DNS address resolution (neither for authoritative servers or recursive caches).
They really aren't any part of the wire DNS protocol for resolving names.
They *are* part of a wire protocol for secondary servers that slave zonefiles from primary servers, but even in that case it's really more a "BIND convention" than a necessity.
Ultimately how you transfer a zone's records from a master server to a slave server is up to however those two servers and their administrators agree to do so.
You can skip the AXFR protocol that uses zonefiles and instead do something else that works for both of you.
Inventing a new method of slaving zone data is easy and doesn't involved much complicated rollout.
Some people just rsync zonefiles for instance instead of using AXFR today.It's really frustrating (believe me, I've done it) when you try to implement a new DNS server daemon from scratch from the RFCs, and you have to wade through this mess of "what's a BIND convention that doesn't matter and what's important to the actual DNS protocol for resolving names on the wire".</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733975</id>
	<title>Re:DNS is the problem</title>
	<author>Skuld-Chan</author>
	<datestamp>1255458300000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>Well in the 1980's when the RFC was written for zone files (1034/1035) it probably sounded like a perfectly sound way to configure this sort of thing, same with DNS in general (RFC's for which were also written in the 1980's).</p><p>If it were invented from scratch today I'm sure it would resemble something like LDAP.</p><p>The fact we haven't had more mass DNS failures like this is actually surprising.</p></htmltext>
<tokenext>Well in the 1980 's when the RFC was written for zone files ( 1034/1035 ) it probably sounded like a perfectly sound way to configure this sort of thing , same with DNS in general ( RFC 's for which were also written in the 1980 's ) .If it were invented from scratch today I 'm sure it would resemble something like LDAP.The fact we have n't had more mass DNS failures like this is actually surprising .</tokentext>
<sentencetext>Well in the 1980's when the RFC was written for zone files (1034/1035) it probably sounded like a perfectly sound way to configure this sort of thing, same with DNS in general (RFC's for which were also written in the 1980's).If it were invented from scratch today I'm sure it would resemble something like LDAP.The fact we haven't had more mass DNS failures like this is actually surprising.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29738535</id>
	<title>It's only Sweden ...</title>
	<author>Dark$ide</author>
	<datestamp>1255434060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>It doesn't matter.<nobr> <wbr></nobr>.SE is only Sweden. If<nobr> <wbr></nobr>.SEX fell off; then the whole Internet would melt down into a small singularity.</htmltext>
<tokenext>It does n't matter .
.SE is only Sweden .
If .SEX fell off ; then the whole Internet would melt down into a small singularity .</tokentext>
<sentencetext>It doesn't matter.
.SE is only Sweden.
If .SEX fell off; then the whole Internet would melt down into a small singularity.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733465</id>
	<title>Re:change control / management, anyone?</title>
	<author>e2d2</author>
	<datestamp>1255456200000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>I'll go one better and say we should try him in a military tribunal and sentenced to hard time in ADX. That will send the world a  message - NO MISTAKES OR ELSE.</p><p>Get real man, this is a human error. Your struggle for perfection baffles my monkey brain.</p></htmltext>
<tokenext>I 'll go one better and say we should try him in a military tribunal and sentenced to hard time in ADX .
That will send the world a message - NO MISTAKES OR ELSE.Get real man , this is a human error .
Your struggle for perfection baffles my monkey brain .</tokentext>
<sentencetext>I'll go one better and say we should try him in a military tribunal and sentenced to hard time in ADX.
That will send the world a  message - NO MISTAKES OR ELSE.Get real man, this is a human error.
Your struggle for perfection baffles my monkey brain.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733251</id>
	<title>Re:change control / management, anyone?</title>
	<author>Aphoxema</author>
	<datestamp>1255455180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It really <em>isn't</em> a big deal. The mistake was made, the world has the opportunity to learn from it and the economic impact was probably small but scalable enough to take seriously.</p><p>Now if it happened again I'd hope action were taken... don't be so vengeful, SuperBanana!</p></htmltext>
<tokenext>It really is n't a big deal .
The mistake was made , the world has the opportunity to learn from it and the economic impact was probably small but scalable enough to take seriously.Now if it happened again I 'd hope action were taken... do n't be so vengeful , SuperBanana !</tokentext>
<sentencetext>It really isn't a big deal.
The mistake was made, the world has the opportunity to learn from it and the economic impact was probably small but scalable enough to take seriously.Now if it happened again I'd hope action were taken... don't be so vengeful, SuperBanana!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733623</id>
	<title>Re:change control / management, anyone?</title>
	<author>Anonymous</author>
	<datestamp>1255456920000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>We ship whatever code we get done by  5 pm. Never had any code problems.</p></div><p>Of course anyone with the described schedule would NEVER have code problems.</p><p>(Except for lack of... LOL)</p></div>
	</htmltext>
<tokenext>We ship whatever code we get done by 5 pm .
Never had any code problems.Of course anyone with the described schedule would NEVER have code problems .
( Except for lack of... LOL )</tokentext>
<sentencetext>We ship whatever code we get done by  5 pm.
Never had any code problems.Of course anyone with the described schedule would NEVER have code problems.
(Except for lack of... LOL)
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733311</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733129</id>
	<title>Ah, the joy of automated oopsies.</title>
	<author>palegray.net</author>
	<datestamp>1255454580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>One missing character, repeated a whole lot of times, results in an entire TLD going offline. Awesome.</htmltext>
<tokenext>One missing character , repeated a whole lot of times , results in an entire TLD going offline .
Awesome .</tokentext>
<sentencetext>One missing character, repeated a whole lot of times, results in an entire TLD going offline.
Awesome.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734543</id>
	<title>Re:change control / management, anyone?</title>
	<author>Burdell</author>
	<datestamp>1255460640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Obviously, it passed syntax-checking, or the server wouldn't have loaded it.  What you are looking for is semantic-checking, which is much more difficult.  I expect that the generation scripts will be expanded to check for more things; that's generally what happens (you check for what you can think of, and expand the checking when someone thinks of a better way to break things).</p><p>Negative caching (in BIND anyway) tops out at 3 hours (it looks like<nobr> <wbr></nobr>.se has it set to 2 hours).  The NS record TTL is 2 days, so only about 1/96 of servers regularly looking up<nobr> <wbr></nobr>.se entries would have made a request during the 30 minute window.</p><p>As for somebody being fired for making one relatively simple mistake: were you fired from McDonald's, Burger King, and Wendy's every time you dropped a fry on the floor?</p><p>ObQuote: "Ok! Ok! I must have, I must have put a decimal point in the wrong place or something. Shit. I always do that. I always mess up some mundane detail."</p></htmltext>
<tokenext>Obviously , it passed syntax-checking , or the server would n't have loaded it .
What you are looking for is semantic-checking , which is much more difficult .
I expect that the generation scripts will be expanded to check for more things ; that 's generally what happens ( you check for what you can think of , and expand the checking when someone thinks of a better way to break things ) .Negative caching ( in BIND anyway ) tops out at 3 hours ( it looks like .se has it set to 2 hours ) .
The NS record TTL is 2 days , so only about 1/96 of servers regularly looking up .se entries would have made a request during the 30 minute window.As for somebody being fired for making one relatively simple mistake : were you fired from McDonald 's , Burger King , and Wendy 's every time you dropped a fry on the floor ? ObQuote : " Ok !
Ok ! I must have , I must have put a decimal point in the wrong place or something .
Shit. I always do that .
I always mess up some mundane detail .
"</tokentext>
<sentencetext>Obviously, it passed syntax-checking, or the server wouldn't have loaded it.
What you are looking for is semantic-checking, which is much more difficult.
I expect that the generation scripts will be expanded to check for more things; that's generally what happens (you check for what you can think of, and expand the checking when someone thinks of a better way to break things).Negative caching (in BIND anyway) tops out at 3 hours (it looks like .se has it set to 2 hours).
The NS record TTL is 2 days, so only about 1/96 of servers regularly looking up .se entries would have made a request during the 30 minute window.As for somebody being fired for making one relatively simple mistake: were you fired from McDonald's, Burger King, and Wendy's every time you dropped a fry on the floor?ObQuote: "Ok!
Ok! I must have, I must have put a decimal point in the wrong place or something.
Shit. I always do that.
I always mess up some mundane detail.
"</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734873</id>
	<title>Re:No big deal</title>
	<author>Anonymous</author>
	<datestamp>1255462080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Nah. In Sweden, when you want to see hot chicks, you just have to go outside. Even looking out the window might suffice. ^^</p></htmltext>
<tokenext>Nah .
In Sweden , when you want to see hot chicks , you just have to go outside .
Even looking out the window might suffice .
^ ^</tokentext>
<sentencetext>Nah.
In Sweden, when you want to see hot chicks, you just have to go outside.
Even looking out the window might suffice.
^^</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735527</id>
	<title>Re:No big deal</title>
	<author>Anonymous</author>
	<datestamp>1255465380000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p><div class="quote"><p>The downtime lasted 30 minutes, and most domains were probably cached by nameservers anyway.</p></div><p>I once viddied an animated documentary about <a href="http://en.wikipedia.org/wiki/Over\_Logging" title="wikipedia.org" rel="nofollow">a small town in Colorado that lost the internet for 22 minutes</a> [wikipedia.org].  It was not pretty.  Our hearts and minds go out to you, people of Sweden.  I cannot even fathom what that would be like<nobr> <wbr></nobr>... I hope the looting and rioting has died down with the restoration of the internet.</p></div><p>That is nothing. In Argentina we DNS problems every 5 o 6 months. Large regions in Argentina can't access the web for hours, and even for days.</p><p>For those who love Adam Smith, in Argentina we have only two ISP providers, Telecom and Telefonica. Telefonica has bougth Telecom, so now we have a BIG monopoly on cell phones, wired phones, and internet services.</p></div>
	</htmltext>
<tokenext>The downtime lasted 30 minutes , and most domains were probably cached by nameservers anyway.I once viddied an animated documentary about a small town in Colorado that lost the internet for 22 minutes [ wikipedia.org ] .
It was not pretty .
Our hearts and minds go out to you , people of Sweden .
I can not even fathom what that would be like ... I hope the looting and rioting has died down with the restoration of the internet.That is nothing .
In Argentina we DNS problems every 5 o 6 months .
Large regions in Argentina ca n't access the web for hours , and even for days.For those who love Adam Smith , in Argentina we have only two ISP providers , Telecom and Telefonica .
Telefonica has bougth Telecom , so now we have a BIG monopoly on cell phones , wired phones , and internet services .</tokentext>
<sentencetext>The downtime lasted 30 minutes, and most domains were probably cached by nameservers anyway.I once viddied an animated documentary about a small town in Colorado that lost the internet for 22 minutes [wikipedia.org].
It was not pretty.
Our hearts and minds go out to you, people of Sweden.
I cannot even fathom what that would be like ... I hope the looting and rioting has died down with the restoration of the internet.That is nothing.
In Argentina we DNS problems every 5 o 6 months.
Large regions in Argentina can't access the web for hours, and even for days.For those who love Adam Smith, in Argentina we have only two ISP providers, Telecom and Telefonica.
Telefonica has bougth Telecom, so now we have a BIG monopoly on cell phones, wired phones, and internet services.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735671</id>
	<title>A moose once bit my DNS...</title>
	<author>AliasMarlowe</author>
	<datestamp>1255465920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>...and the DNS bit everyone else.</htmltext>
<tokenext>...and the DNS bit everyone else .</tokentext>
<sentencetext>...and the DNS bit everyone else.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734263</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732987</id>
	<title>Re:No big deal</title>
	<author>Anonymous</author>
	<datestamp>1255453860000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p><div class="quote"><p>The downtime lasted 30 minutes, and most domains were probably cached by nameservers anyway.</p></div><p>I once viddied an animated documentary about <a href="http://en.wikipedia.org/wiki/Over\_Logging" title="wikipedia.org">a small town in Colorado that lost the internet for 22 minutes</a> [wikipedia.org].  It was not pretty.  Our hearts and minds go out to you, people of Sweden.  I cannot even fathom what that would be like<nobr> <wbr></nobr>... I hope the looting and rioting has died down with the restoration of the internet.</p></div>
	</htmltext>
<tokenext>The downtime lasted 30 minutes , and most domains were probably cached by nameservers anyway.I once viddied an animated documentary about a small town in Colorado that lost the internet for 22 minutes [ wikipedia.org ] .
It was not pretty .
Our hearts and minds go out to you , people of Sweden .
I can not even fathom what that would be like ... I hope the looting and rioting has died down with the restoration of the internet .</tokentext>
<sentencetext>The downtime lasted 30 minutes, and most domains were probably cached by nameservers anyway.I once viddied an animated documentary about a small town in Colorado that lost the internet for 22 minutes [wikipedia.org].
It was not pretty.
Our hearts and minds go out to you, people of Sweden.
I cannot even fathom what that would be like ... I hope the looting and rioting has died down with the restoration of the internet.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733287</id>
	<title>The trailing dot!</title>
	<author>Anonymous</author>
	<datestamp>1255455360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Well then, the title should be: Entire<nobr> <wbr></nobr>.SE<strong> <strong><nobr> <wbr></nobr><strong>.</strong> </strong> </strong> TLD Drops off the internet</p></htmltext>
<tokenext>Well then , the title should be : Entire .SE .
TLD Drops off the internet</tokentext>
<sentencetext>Well then, the title should be: Entire .SE  .
TLD Drops off the internet</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734409</id>
	<title>Re:change control / management, anyone?</title>
	<author>Anonymous</author>
	<datestamp>1255460100000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Of course they stage this kind of stuff. It's a top level domain. Do you think they would get the contact to run it if they didn't? In one of the world's most wired nations? (Together with other northern European states and South Korea.)</p><p>Somehow a bug in the script that moved out the zone to production caused this. And none of the tests caught it. We don't know the details yet. But it caused big disruptions, that's for sure.</p><p>Also, upgrade from a 386? A TLD with a million records and running dnssec in production? I don't think you fully understand the scope of running these things. The talk about negative caching also leads me to believe you haven't thought this through.</p></htmltext>
<tokenext>Of course they stage this kind of stuff .
It 's a top level domain .
Do you think they would get the contact to run it if they did n't ?
In one of the world 's most wired nations ?
( Together with other northern European states and South Korea .
) Somehow a bug in the script that moved out the zone to production caused this .
And none of the tests caught it .
We do n't know the details yet .
But it caused big disruptions , that 's for sure.Also , upgrade from a 386 ?
A TLD with a million records and running dnssec in production ?
I do n't think you fully understand the scope of running these things .
The talk about negative caching also leads me to believe you have n't thought this through .</tokentext>
<sentencetext>Of course they stage this kind of stuff.
It's a top level domain.
Do you think they would get the contact to run it if they didn't?
In one of the world's most wired nations?
(Together with other northern European states and South Korea.
)Somehow a bug in the script that moved out the zone to production caused this.
And none of the tests caught it.
We don't know the details yet.
But it caused big disruptions, that's for sure.Also, upgrade from a 386?
A TLD with a million records and running dnssec in production?
I don't think you fully understand the scope of running these things.
The talk about negative caching also leads me to believe you haven't thought this through.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733381</id>
	<title>It was goat.se's fault</title>
	<author>Anonymous</author>
	<datestamp>1255455720000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><a href="http://goat.se/cx/" title="goat.se" rel="nofollow">His "cx" blocked the tubes</a> [goat.se]</p></htmltext>
<tokenext>His " cx " blocked the tubes [ goat.se ]</tokentext>
<sentencetext>His "cx" blocked the tubes [goat.se]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734243</id>
	<title>Re:No big deal</title>
	<author>Anonymous</author>
	<datestamp>1255459380000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p> I hope they'll learn their lesson from this and change their procedures.</p></div><p> <a href="http://www.translate.google.com/translate\_t#sv\%7Cen\%7CDu\%20m\%C3\%A5ste\%20vara\%20ny\%20h\%C3\%A4r." title="google.com" rel="nofollow"> Du m&#229;ste vara ny h&#228;r.</a> [google.com]</p></div>
	</htmltext>
<tokenext>I hope they 'll learn their lesson from this and change their procedures .
Du m   ste vara ny h   r .
[ google.com ]</tokentext>
<sentencetext> I hope they'll learn their lesson from this and change their procedures.
Du måste vara ny här.
[google.com]
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733561</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732953</id>
	<title>I downloaded..</title>
	<author>Anonymous</author>
	<datestamp>1255453680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>it all off Pirate Bay already.</p></htmltext>
<tokenext>it all off Pirate Bay already .</tokentext>
<sentencetext>it all off Pirate Bay already.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733245</id>
	<title>sweden is in scandinavia which is thule</title>
	<author>circletimessquare</author>
	<datestamp>1255455120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><a href="http://en.wikipedia.org/wiki/Thule" title="wikipedia.org" rel="nofollow">http://en.wikipedia.org/wiki/Thule</a> [wikipedia.org]</p><p>we all know that thule is the ends of the earth</p><p>so none of us should be surprised. it should have been anticipated that sweden would drop off the earth at some point. today's that day apparently</p></htmltext>
<tokenext>http : //en.wikipedia.org/wiki/Thule [ wikipedia.org ] we all know that thule is the ends of the earthso none of us should be surprised .
it should have been anticipated that sweden would drop off the earth at some point .
today 's that day apparently</tokentext>
<sentencetext>http://en.wikipedia.org/wiki/Thule [wikipedia.org]we all know that thule is the ends of the earthso none of us should be surprised.
it should have been anticipated that sweden would drop off the earth at some point.
today's that day apparently</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29739653</id>
	<title>Re:change control / management, anyone?</title>
	<author>turbidostato</author>
	<datestamp>1255441980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>"I would expect that at the TLD level, a change to a configuration file would have to be inspected by someone AND run through some syntax-checking scripts..."</p><p>Expect price and time-to-activation increase for second level domains way beyond current status then.</p><p>"DNS servers (and individual computers!) cache negative results."</p><p>Yeah, but in practice only for individual resources, not whole domains, since negative answers from authoritative sources must include SOA references as per RFC2308.</p><p>"Anything anyone did a query on during those 30 minutes will be negatively cached by their system and their local DNS server"</p><p>Now you know what happens when you are in a hurry and ask for a to-be-activated resource prior to its inclusion on the zone.</p><p>"but it's still going to seriously impact traffic to many, many sites, especially for everyone outside Sweden."</p><p>The fact is, well, it won't.</p></htmltext>
<tokenext>" I would expect that at the TLD level , a change to a configuration file would have to be inspected by someone AND run through some syntax-checking scripts... " Expect price and time-to-activation increase for second level domains way beyond current status then .
" DNS servers ( and individual computers !
) cache negative results .
" Yeah , but in practice only for individual resources , not whole domains , since negative answers from authoritative sources must include SOA references as per RFC2308 .
" Anything anyone did a query on during those 30 minutes will be negatively cached by their system and their local DNS server " Now you know what happens when you are in a hurry and ask for a to-be-activated resource prior to its inclusion on the zone .
" but it 's still going to seriously impact traffic to many , many sites , especially for everyone outside Sweden .
" The fact is , well , it wo n't .</tokentext>
<sentencetext>"I would expect that at the TLD level, a change to a configuration file would have to be inspected by someone AND run through some syntax-checking scripts..."Expect price and time-to-activation increase for second level domains way beyond current status then.
"DNS servers (and individual computers!
) cache negative results.
"Yeah, but in practice only for individual resources, not whole domains, since negative answers from authoritative sources must include SOA references as per RFC2308.
"Anything anyone did a query on during those 30 minutes will be negatively cached by their system and their local DNS server"Now you know what happens when you are in a hurry and ask for a to-be-activated resource prior to its inclusion on the zone.
"but it's still going to seriously impact traffic to many, many sites, especially for everyone outside Sweden.
"The fact is, well, it won't.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734093</id>
	<title>Re:No big deal</title>
	<author>Anonymous</author>
	<datestamp>1255458780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>No big deal? <i>No big deal???</i> Where the hell else am I supposed to go to look at pictures of hot Swedish women hitting the nightclub scene (in a way that's at least a little SFW) if I can't get to <a href="http://www.thelocal.se/" title="thelocal.se">http://www.thelocal.se/</a> [thelocal.se]?</p></htmltext>
<tokenext>No big deal ?
No big deal ? ? ?
Where the hell else am I supposed to go to look at pictures of hot Swedish women hitting the nightclub scene ( in a way that 's at least a little SFW ) if I ca n't get to http : //www.thelocal.se/ [ thelocal.se ] ?</tokentext>
<sentencetext>No big deal?
No big deal???
Where the hell else am I supposed to go to look at pictures of hot Swedish women hitting the nightclub scene (in a way that's at least a little SFW) if I can't get to http://www.thelocal.se/ [thelocal.se]?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29753845</id>
	<title>Turn it over to a woman to manage</title>
	<author>Artifex</author>
	<datestamp>1255547460000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Guarantee she'd detect a missing period earlier.</p></htmltext>
<tokenext>Guarantee she 'd detect a missing period earlier .</tokentext>
<sentencetext>Guarantee she'd detect a missing period earlier.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315</id>
	<title>DNS is the problem</title>
	<author>Anonymous</author>
	<datestamp>1255455420000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>4</modscore>
	<htmltext>It still boggles my mind that anyone thought zone files are a good idea.  The file format is so damn brittle, that a single byte can spell disaster.  On top of that, the hierarchical naming structure presents an inherent systemic risk for all sub-domains as exhibited by this<nobr> <wbr></nobr>.se fiasco.  Nevermind the injection attacks, Pakistan taking out Youtube, and the rest, you have organizations like Verisign which profit immensely off of keeping the system broken.  And don't even bother mentioning DNSSEC, as it still doesn't resolve this fundamental issue.  The next systemic fuckup will simply be a signed fuckup.</htmltext>
<tokenext>It still boggles my mind that anyone thought zone files are a good idea .
The file format is so damn brittle , that a single byte can spell disaster .
On top of that , the hierarchical naming structure presents an inherent systemic risk for all sub-domains as exhibited by this .se fiasco .
Nevermind the injection attacks , Pakistan taking out Youtube , and the rest , you have organizations like Verisign which profit immensely off of keeping the system broken .
And do n't even bother mentioning DNSSEC , as it still does n't resolve this fundamental issue .
The next systemic fuckup will simply be a signed fuckup .</tokentext>
<sentencetext>It still boggles my mind that anyone thought zone files are a good idea.
The file format is so damn brittle, that a single byte can spell disaster.
On top of that, the hierarchical naming structure presents an inherent systemic risk for all sub-domains as exhibited by this .se fiasco.
Nevermind the injection attacks, Pakistan taking out Youtube, and the rest, you have organizations like Verisign which profit immensely off of keeping the system broken.
And don't even bother mentioning DNSSEC, as it still doesn't resolve this fundamental issue.
The next systemic fuckup will simply be a signed fuckup.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733997</id>
	<title>Re:change control / management, anyone?</title>
	<author>marc\_gerges</author>
	<datestamp>1255458420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I seriously hope someone is fired or loses a contract over this.</p></div><p>It seems a silly idea to fire somebody just after having invested $(whatever\_this\_snafu\_is\_supposed\_to\_have\_cost) into his education.</p></div>
	</htmltext>
<tokenext>I seriously hope someone is fired or loses a contract over this.It seems a silly idea to fire somebody just after having invested $ ( whatever \ _this \ _snafu \ _is \ _supposed \ _to \ _have \ _cost ) into his education .</tokentext>
<sentencetext>I seriously hope someone is fired or loses a contract over this.It seems a silly idea to fire somebody just after having invested $(whatever\_this\_snafu\_is\_supposed\_to\_have\_cost) into his education.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734859</id>
	<title>Re:So I guess it's...</title>
	<author>Verdatum</author>
	<datestamp>1255462020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I can't believe I had to scroll through this many comments to find the first BORK joke!  I was starting to get nervous!</htmltext>
<tokenext>I ca n't believe I had to scroll through this many comments to find the first BORK joke !
I was starting to get nervous !</tokentext>
<sentencetext>I can't believe I had to scroll through this many comments to find the first BORK joke!
I was starting to get nervous!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733093</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733295</id>
	<title>somewhere in sweden:</title>
	<author>nimbius</author>
	<datestamp>1255455360000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>an admin has popped back from lunch and asked, "hey guys did someone turn my computer off while i was gone?   there was a file i was working on......"</htmltext>
<tokenext>an admin has popped back from lunch and asked , " hey guys did someone turn my computer off while i was gone ?
there was a file i was working on...... "</tokentext>
<sentencetext>an admin has popped back from lunch and asked, "hey guys did someone turn my computer off while i was gone?
there was a file i was working on......"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733621</id>
	<title>Re:change control / management, anyone?</title>
	<author>Anonymous</author>
	<datestamp>1255456920000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Yeah, you don't live in Sweden, that's what I'm hearing.</p><p>Fire someone for making a mistake or error? Not in this country.</p><p>Sweden, where the unions protect your ass</p></htmltext>
<tokenext>Yeah , you do n't live in Sweden , that 's what I 'm hearing.Fire someone for making a mistake or error ?
Not in this country.Sweden , where the unions protect your ass</tokentext>
<sentencetext>Yeah, you don't live in Sweden, that's what I'm hearing.Fire someone for making a mistake or error?
Not in this country.Sweden, where the unions protect your ass</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733119</id>
	<title>Let me be the first to say:</title>
	<author>Anonymous</author>
	<datestamp>1255454580000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>bork, bork, bork...</p></htmltext>
<tokenext>bork , bork , bork.. .</tokentext>
<sentencetext>bork, bork, bork...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734871</id>
	<title>Re:An oft overlooked single point of failure?</title>
	<author>flyingfsck</author>
	<datestamp>1255462080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>No, it was a single dot of failure.</htmltext>
<tokenext>No , it was a single dot of failure .</tokentext>
<sentencetext>No, it was a single dot of failure.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733971</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29741233</id>
	<title>the internet is like a swedish bikini model</title>
	<author>gemada</author>
	<datestamp>1255456680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>you don't realize how valuable they are until they go down on you.</htmltext>
<tokenext>you do n't realize how valuable they are until they go down on you .</tokentext>
<sentencetext>you don't realize how valuable they are until they go down on you.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734975</id>
	<title>Re:change control / management, anyone?</title>
	<author>rs79</author>
	<datestamp>1255462740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It's not "a" dot, it's "every" dot. A bad script adn DNSSEC are to blame. Note that this is version 4 (5?) of dnssec. The earlier ones just didn't work.</p><p>And there's a real bad gotcha in the current one they haven't found yet that has still to raise it's ugly head. In time.</p></htmltext>
<tokenext>It 's not " a " dot , it 's " every " dot .
A bad script adn DNSSEC are to blame .
Note that this is version 4 ( 5 ?
) of dnssec .
The earlier ones just did n't work.And there 's a real bad gotcha in the current one they have n't found yet that has still to raise it 's ugly head .
In time .</tokentext>
<sentencetext>It's not "a" dot, it's "every" dot.
A bad script adn DNSSEC are to blame.
Note that this is version 4 (5?
) of dnssec.
The earlier ones just didn't work.And there's a real bad gotcha in the current one they haven't found yet that has still to raise it's ugly head.
In time.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735629</id>
	<title>Re:There goes my favorite web site !</title>
	<author>Anonymous</author>
	<datestamp>1255465680000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p><div class="quote"><p>Goat.se</p></div><p>Arrgh... the horror... <a href="http://goat.se/cx" title="goat.se">http://goat.se/cx</a> [goat.se] You'll want to claw your eyes out!</p></div>
	</htmltext>
<tokenext>Goat.seArrgh... the horror... http : //goat.se/cx [ goat.se ] You 'll want to claw your eyes out !</tokentext>
<sentencetext>Goat.seArrgh... the horror... http://goat.se/cx [goat.se] You'll want to claw your eyes out!
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732903</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734951</id>
	<title>Re:No big deal</title>
	<author>CorporateSuit</author>
	<datestamp>1255462500000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p><div class="quote"><p>DNS is very simple, but it's just as prone to human error as anything else.</p></div><p>Are you kidding?  I've been programming DNS for a long time, and if theirs one thing I learned, its that programmers like me don't make errors.</p></div>
	</htmltext>
<tokenext>DNS is very simple , but it 's just as prone to human error as anything else.Are you kidding ?
I 've been programming DNS for a long time , and if theirs one thing I learned , its that programmers like me do n't make errors .</tokentext>
<sentencetext>DNS is very simple, but it's just as prone to human error as anything else.Are you kidding?
I've been programming DNS for a long time, and if theirs one thing I learned, its that programmers like me don't make errors.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733561</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735147</id>
	<title>Re:There goes my favorite web site !</title>
	<author>hldn</author>
	<datestamp>1255463640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>that is a handsome looking fellow on that site.</p></htmltext>
<tokenext>that is a handsome looking fellow on that site .</tokentext>
<sentencetext>that is a handsome looking fellow on that site.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732903</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734615</id>
	<title>Re:change control / management, anyone?</title>
	<author>yffe</author>
	<datestamp>1255460940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I seriously hope someone is fired or loses a contract over this.</p></div><p>No, they got <a href="http://photos-g.ak.fbcdn.net/hphotos-ak-snc1/hs232.snc1/7931\_157722341890\_566661890\_3229966\_8050244\_n.jpg" title="fbcdn.net" rel="nofollow">cake</a> [fbcdn.net].</p></div>
	</htmltext>
<tokenext>I seriously hope someone is fired or loses a contract over this.No , they got cake [ fbcdn.net ] .</tokentext>
<sentencetext>I seriously hope someone is fired or loses a contract over this.No, they got cake [fbcdn.net].
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29737071</id>
	<title>Re:No big deal</title>
	<author>dmmiller2k</author>
	<datestamp>1255428240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>So apparently it was nothing like the South Park episode where South Park lost its internet.</htmltext>
<tokenext>So apparently it was nothing like the South Park episode where South Park lost its internet .</tokentext>
<sentencetext>So apparently it was nothing like the South Park episode where South Park lost its internet.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732987</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734583</id>
	<title>Re:DNS is the problem</title>
	<author>Kynde</author>
	<datestamp>1255460820000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p><i>The file format is so damn brittle, that a single byte can spell disaster.</i></p><p>You know what, so is ELF. Who said you should write zonefiles by hand let alone without any kind of syntax verification.</p><p>Input syntax is never really an issue. You only ever lack the necessary tools or you are unable to use them properly. It can always be hidden behind a precompiler or whatever necessary.</p><p>Hmmm... wait, termcap. I stand corrected.</p></htmltext>
<tokenext>The file format is so damn brittle , that a single byte can spell disaster.You know what , so is ELF .
Who said you should write zonefiles by hand let alone without any kind of syntax verification.Input syntax is never really an issue .
You only ever lack the necessary tools or you are unable to use them properly .
It can always be hidden behind a precompiler or whatever necessary.Hmmm... wait , termcap .
I stand corrected .</tokentext>
<sentencetext>The file format is so damn brittle, that a single byte can spell disaster.You know what, so is ELF.
Who said you should write zonefiles by hand let alone without any kind of syntax verification.Input syntax is never really an issue.
You only ever lack the necessary tools or you are unable to use them properly.
It can always be hidden behind a precompiler or whatever necessary.Hmmm... wait, termcap.
I stand corrected.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732877</id>
	<title>TPB</title>
	<author>Anonymous</author>
	<datestamp>1255453380000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext>They are going to extremes in Sweden to get thepiratebay.org off the internet!</htmltext>
<tokenext>They are going to extremes in Sweden to get thepiratebay.org off the internet !</tokentext>
<sentencetext>They are going to extremes in Sweden to get thepiratebay.org off the internet!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733667</id>
	<title>Re:change control / management, anyone?</title>
	<author>Anonymous</author>
	<datestamp>1255457100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I hope you get fired when you make you a mistake.</p></htmltext>
<tokenext>I hope you get fired when you make you a mistake .</tokentext>
<sentencetext>I hope you get fired when you make you a mistake.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733449</id>
	<title>Re:DNS is the problem</title>
	<author>upside</author>
	<datestamp>1255456140000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext><p>Except the Pakistan affair was about the BGP routing protocol. I agree the file format is nutty, though.</p><p>I can't think of a better alternative to the hierarchical system, perhaps you have a suggestion. A flat namespace would be an administrative impossiblity, not to mention the stress it would put on name servers. Increasing the number of TLDs would lessen the impact of a single failure, though.</p></htmltext>
<tokenext>Except the Pakistan affair was about the BGP routing protocol .
I agree the file format is nutty , though.I ca n't think of a better alternative to the hierarchical system , perhaps you have a suggestion .
A flat namespace would be an administrative impossiblity , not to mention the stress it would put on name servers .
Increasing the number of TLDs would lessen the impact of a single failure , though .</tokentext>
<sentencetext>Except the Pakistan affair was about the BGP routing protocol.
I agree the file format is nutty, though.I can't think of a better alternative to the hierarchical system, perhaps you have a suggestion.
A flat namespace would be an administrative impossiblity, not to mention the stress it would put on name servers.
Increasing the number of TLDs would lessen the impact of a single failure, though.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733589</id>
	<title>Re:change control / management, anyone?</title>
	<author>Anonymous</author>
	<datestamp>1255456680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Wow, what a whiny little brat you are. Did mummsy drop wyou on your heady-boos?</p></htmltext>
<tokenext>Wow , what a whiny little brat you are .
Did mummsy drop wyou on your heady-boos ?</tokentext>
<sentencetext>Wow, what a whiny little brat you are.
Did mummsy drop wyou on your heady-boos?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733739</id>
	<title>Re:change control / management, anyone?</title>
	<author>Phred T. Magnificent</author>
	<datestamp>1255457400000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>If this is the first time the responsible party has made a mistake like this, then it probably doesn't need to be a career-terminating experience.</p><p>With that said, though, you're entirely right that there should have been validation and change control!</p></htmltext>
<tokenext>If this is the first time the responsible party has made a mistake like this , then it probably does n't need to be a career-terminating experience.With that said , though , you 're entirely right that there should have been validation and change control !</tokentext>
<sentencetext>If this is the first time the responsible party has made a mistake like this, then it probably doesn't need to be a career-terminating experience.With that said, though, you're entirely right that there should have been validation and change control!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733093</id>
	<title>So I guess it's...</title>
	<author>Anonymous</author>
	<datestamp>1255454460000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>...borked!</htmltext>
<tokenext>...borked !</tokentext>
<sentencetext>...borked!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733971</id>
	<title>Re:An oft overlooked single point of failure?</title>
	<author>Anonymous</author>
	<datestamp>1255458300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You can't protect against a single point of failure when you're talking about a person updating a system. Redundancy protects against computer error, not human error.</p><p>See, ultimately, somebody, somewhere has to be responsible for the name updating. Having it in two places just means that an incorrect update gets pushed to both places by the person making the change.</p><p>In this case, the effects were minimized by the nature of DNS itself, and the caching mechanisms involved. Most servers probably never saw the changes. Those that did will get their caches cleared fairly rapidly, and the effect is minimal.</p></htmltext>
<tokenext>You ca n't protect against a single point of failure when you 're talking about a person updating a system .
Redundancy protects against computer error , not human error.See , ultimately , somebody , somewhere has to be responsible for the name updating .
Having it in two places just means that an incorrect update gets pushed to both places by the person making the change.In this case , the effects were minimized by the nature of DNS itself , and the caching mechanisms involved .
Most servers probably never saw the changes .
Those that did will get their caches cleared fairly rapidly , and the effect is minimal .</tokentext>
<sentencetext>You can't protect against a single point of failure when you're talking about a person updating a system.
Redundancy protects against computer error, not human error.See, ultimately, somebody, somewhere has to be responsible for the name updating.
Having it in two places just means that an incorrect update gets pushed to both places by the person making the change.In this case, the effects were minimized by the nature of DNS itself, and the caching mechanisms involved.
Most servers probably never saw the changes.
Those that did will get their caches cleared fairly rapidly, and the effect is minimal.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733003</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734833</id>
	<title>Re:change control / management, anyone?</title>
	<author>Verdatum</author>
	<datestamp>1255461840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><tt>10 PRINT "Please manage airplane fuel."<br>
20 GOTO 10 </tt></htmltext>
<tokenext>10 PRINT " Please manage airplane fuel .
" 20 GOTO 10</tokentext>
<sentencetext>10 PRINT "Please manage airplane fuel.
"
20 GOTO 10 </sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733311</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734263</id>
	<title>There's m&oslash;re to Sweden than .se</title>
	<author>Anonymous</author>
	<datestamp>1255459500000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>Wi n&#248;t trei a h&oslash;liday in Sweden this yer?</p><p>See the l&oslash;veli lakes</p><p>The wonderful teleph&oslash;ne system</p><p>And mani interesting furry animals</p></htmltext>
<tokenext>Wi n   t trei a h   liday in Sweden this yer ? See the l   veli lakesThe wonderful teleph   ne systemAnd mani interesting furry animals</tokentext>
<sentencetext>Wi nøt trei a høliday in Sweden this yer?See the løveli lakesThe wonderful telephøne systemAnd mani interesting furry animals</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734451</id>
	<title>Re:change control / management, anyone?</title>
	<author>Chris Mattern</author>
	<datestamp>1255460280000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><blockquote><div><p>Even more helpfully, most tools won't notice and the zone will pass a configuration check because missing the trailing "." is syntactically correct.</p></div></blockquote><p>Not if the configuration check you wrote checks for the trailing "." anyways.  And if it doesn't, you need to rewrite it.</p></div>
	</htmltext>
<tokenext>Even more helpfully , most tools wo n't notice and the zone will pass a configuration check because missing the trailing " .
" is syntactically correct.Not if the configuration check you wrote checks for the trailing " .
" anyways .
And if it does n't , you need to rewrite it .</tokentext>
<sentencetext>Even more helpfully, most tools won't notice and the zone will pass a configuration check because missing the trailing ".
" is syntactically correct.Not if the configuration check you wrote checks for the trailing ".
" anyways.
And if it doesn't, you need to rewrite it.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734063</id>
	<title>Re:change control / management, anyone?</title>
	<author>Anonymous</author>
	<datestamp>1255458600000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>As a DNS admin myself, touching high value zones, let me tell you, missing a stupid dot happens all the time.  All the change control in the world doesn't help when you just don't type one little period.  Even more helpfully, most tools won't notice and the zone will pass a configuration check because missing the trailing "." is syntactically correct.</p><p>Let me add as well that "change management" that you want is just fantastic<nobr> <wbr></nobr>.. no making changes during core hours.  When you run a 24/7 business, non-core hours means something like 2am.  at 2am, I, and most mammals, are not at their mental best, so missing a single dot isn't horribly hard.</p><p>The only thing I'd suggest they do is use an offline test box for zones, then promote that change to prod.  Then, you can load all the mistakes you want, do your digs, and if stuff works, THEN you move it to prod.  I never ever make changes on production servers, they are done offline, tested, then put into prod with scripts.  It makes it a lot harder for missing periods to make it into production.</p><p>Finally, this is a good reason why negative caching should have low TTLs.  If you run a DNS server that can't handle low neg-caching TTLs, it's time to upgrade from a 386.</p><p>Cheers.</p></htmltext>
<tokenext>As a DNS admin myself , touching high value zones , let me tell you , missing a stupid dot happens all the time .
All the change control in the world does n't help when you just do n't type one little period .
Even more helpfully , most tools wo n't notice and the zone will pass a configuration check because missing the trailing " .
" is syntactically correct.Let me add as well that " change management " that you want is just fantastic .. no making changes during core hours .
When you run a 24/7 business , non-core hours means something like 2am .
at 2am , I , and most mammals , are not at their mental best , so missing a single dot is n't horribly hard.The only thing I 'd suggest they do is use an offline test box for zones , then promote that change to prod .
Then , you can load all the mistakes you want , do your digs , and if stuff works , THEN you move it to prod .
I never ever make changes on production servers , they are done offline , tested , then put into prod with scripts .
It makes it a lot harder for missing periods to make it into production.Finally , this is a good reason why negative caching should have low TTLs .
If you run a DNS server that ca n't handle low neg-caching TTLs , it 's time to upgrade from a 386.Cheers .</tokentext>
<sentencetext>As a DNS admin myself, touching high value zones, let me tell you, missing a stupid dot happens all the time.
All the change control in the world doesn't help when you just don't type one little period.
Even more helpfully, most tools won't notice and the zone will pass a configuration check because missing the trailing ".
" is syntactically correct.Let me add as well that "change management" that you want is just fantastic .. no making changes during core hours.
When you run a 24/7 business, non-core hours means something like 2am.
at 2am, I, and most mammals, are not at their mental best, so missing a single dot isn't horribly hard.The only thing I'd suggest they do is use an offline test box for zones, then promote that change to prod.
Then, you can load all the mistakes you want, do your digs, and if stuff works, THEN you move it to prod.
I never ever make changes on production servers, they are done offline, tested, then put into prod with scripts.
It makes it a lot harder for missing periods to make it into production.Finally, this is a good reason why negative caching should have low TTLs.
If you run a DNS server that can't handle low neg-caching TTLs, it's time to upgrade from a 386.Cheers.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734651</id>
	<title>Re:change control / management, anyone?</title>
	<author>Krneki</author>
	<datestamp>1255461060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Chill out dude. Go got a beer or a coffee, life is too good to waste it complaining about problems.<br><br>And if you get so emotional for 30min of Internet downtime you will probably die out of stress too soon.</htmltext>
<tokenext>Chill out dude .
Go got a beer or a coffee , life is too good to waste it complaining about problems.And if you get so emotional for 30min of Internet downtime you will probably die out of stress too soon .</tokentext>
<sentencetext>Chill out dude.
Go got a beer or a coffee, life is too good to waste it complaining about problems.And if you get so emotional for 30min of Internet downtime you will probably die out of stress too soon.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733863</id>
	<title>Re:unless you are swedish</title>
	<author>Gilmoure</author>
	<datestamp>1255457940000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext><p>Cache your porn, folks. Just sayin'.</p></htmltext>
<tokenext>Cache your porn , folks .
Just sayin' .</tokentext>
<sentencetext>Cache your porn, folks.
Just sayin'.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733277</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</id>
	<title>change control / management, anyone?</title>
	<author>Anonymous</author>
	<datestamp>1255454280000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext><p>I seriously hope someone is fired or loses a contract over this.  Where was the validation, change control, etc?  I would expect that at the TLD level, a change to a configuration file would have to be inspected by someone AND run through some syntax-checking scripts...</p><p>As for the person who was modded up for saying "hey, no big deal, fixed in 30 minutes!", not quite.  DNS servers (and individual computers!) cache negative results.  Anything anyone did a query on during those 30 minutes will be negatively cached by their system and their local DNS server.  Granted, a whole lot of local Swedish ISPs and network providers have probably flushed their DNS server caches, but it's still going to seriously impact traffic to many, many sites, especially for everyone outside Sweden.</p></htmltext>
<tokenext>I seriously hope someone is fired or loses a contract over this .
Where was the validation , change control , etc ?
I would expect that at the TLD level , a change to a configuration file would have to be inspected by someone AND run through some syntax-checking scripts...As for the person who was modded up for saying " hey , no big deal , fixed in 30 minutes !
" , not quite .
DNS servers ( and individual computers !
) cache negative results .
Anything anyone did a query on during those 30 minutes will be negatively cached by their system and their local DNS server .
Granted , a whole lot of local Swedish ISPs and network providers have probably flushed their DNS server caches , but it 's still going to seriously impact traffic to many , many sites , especially for everyone outside Sweden .</tokentext>
<sentencetext>I seriously hope someone is fired or loses a contract over this.
Where was the validation, change control, etc?
I would expect that at the TLD level, a change to a configuration file would have to be inspected by someone AND run through some syntax-checking scripts...As for the person who was modded up for saying "hey, no big deal, fixed in 30 minutes!
", not quite.
DNS servers (and individual computers!
) cache negative results.
Anything anyone did a query on during those 30 minutes will be negatively cached by their system and their local DNS server.
Granted, a whole lot of local Swedish ISPs and network providers have probably flushed their DNS server caches, but it's still going to seriously impact traffic to many, many sites, especially for everyone outside Sweden.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29739549</id>
	<title>Re:An oft overlooked single point of failure?</title>
	<author>turbidostato</author>
	<datestamp>1255441200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>"In this case, the effects were minimized by the nature of DNS itself"</p><p>Well, at least somebody shows some common sense.</p><p>Of course, losing a whole TLD even if only for half an hour is a shame probably the one that did it won't include in his resume, but the fact is that nobody will expend more on secure a resource than it's very value.  DNS is basically distributed, cached information described on plain text files; if an update works (which is vastly most of the time), it works; if it isn't you detect the failure within seconds (logs at reload), it is not so tragical (the previous information will be cached through the Internet), it's easy to spot (is a diff away) and you can easily revert to the previous version plus higher serial number in the meantime.  No need for triplechecks that triplicates the costs and will bring in their own share of bugs to the equation.</p></htmltext>
<tokenext>" In this case , the effects were minimized by the nature of DNS itself " Well , at least somebody shows some common sense.Of course , losing a whole TLD even if only for half an hour is a shame probably the one that did it wo n't include in his resume , but the fact is that nobody will expend more on secure a resource than it 's very value .
DNS is basically distributed , cached information described on plain text files ; if an update works ( which is vastly most of the time ) , it works ; if it is n't you detect the failure within seconds ( logs at reload ) , it is not so tragical ( the previous information will be cached through the Internet ) , it 's easy to spot ( is a diff away ) and you can easily revert to the previous version plus higher serial number in the meantime .
No need for triplechecks that triplicates the costs and will bring in their own share of bugs to the equation .</tokentext>
<sentencetext>"In this case, the effects were minimized by the nature of DNS itself"Well, at least somebody shows some common sense.Of course, losing a whole TLD even if only for half an hour is a shame probably the one that did it won't include in his resume, but the fact is that nobody will expend more on secure a resource than it's very value.
DNS is basically distributed, cached information described on plain text files; if an update works (which is vastly most of the time), it works; if it isn't you detect the failure within seconds (logs at reload), it is not so tragical (the previous information will be cached through the Internet), it's easy to spot (is a diff away) and you can easily revert to the previous version plus higher serial number in the meantime.
No need for triplechecks that triplicates the costs and will bring in their own share of bugs to the equation.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733971</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733335</id>
	<title>Re:change control / management, anyone?</title>
	<author>soup4you2</author>
	<datestamp>1255455480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Might be a small issue, but no reason to get somebody fired over..  People make mistakes all the time.</htmltext>
<tokenext>Might be a small issue , but no reason to get somebody fired over.. People make mistakes all the time .</tokentext>
<sentencetext>Might be a small issue, but no reason to get somebody fired over..  People make mistakes all the time.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734707</id>
	<title>N&#246; There's N&#246;t!</title>
	<author>andersh</author>
	<datestamp>1255461360000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>The Swedish alphabet does not have the letter "&#248;",  it's written "&#246;" in Swedish. The letter "&#248;" is found in Danish and Norwegian.</p><p>The letter is NOT a ligature or a diacritical variant of the letter o! The vowel it sounds most like is the vowel in "bird" or "hurt".</p></htmltext>
<tokenext>The Swedish alphabet does not have the letter "   " , it 's written "   " in Swedish .
The letter "   " is found in Danish and Norwegian.The letter is NOT a ligature or a diacritical variant of the letter o !
The vowel it sounds most like is the vowel in " bird " or " hurt " .</tokentext>
<sentencetext>The Swedish alphabet does not have the letter "ø",  it's written "ö" in Swedish.
The letter "ø" is found in Danish and Norwegian.The letter is NOT a ligature or a diacritical variant of the letter o!
The vowel it sounds most like is the vowel in "bird" or "hurt".</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734263</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734383</id>
	<title>Re:unless you are swedish</title>
	<author>Anonymous</author>
	<datestamp>1255460040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I never noticed that anything was down...</p><p>hmm slashdot.org   wikipedia.org   mywebmailthatIwontslashvertise.fm thepiratebay.org  Guess only my online bank and local news source use<nobr> <wbr></nobr>.se , didn't have need for either at the time.<nobr> <wbr></nobr>/cheers from the polarbears</p></htmltext>
<tokenext>I never noticed that anything was down...hmm slashdot.org wikipedia.org mywebmailthatIwontslashvertise.fm thepiratebay.org Guess only my online bank and local news source use .se , did n't have need for either at the time .
/cheers from the polarbears</tokentext>
<sentencetext>I never noticed that anything was down...hmm slashdot.org   wikipedia.org   mywebmailthatIwontslashvertise.fm thepiratebay.org  Guess only my online bank and local news source use .se , didn't have need for either at the time.
/cheers from the polarbears</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733179</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733311</id>
	<title>Re:change control / management, anyone?</title>
	<author>Anonymous</author>
	<datestamp>1255455420000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>F*** You! I right code for airplane fuel management systems and there is no need for review or even testing. Design is almost non-existent, too. Our design process goes as follows Late on Thursday with a Friday deadline. We go out to our local bar for some drinks. After, a bit of squabbling we right the requirement down on some napkins; pick our programming language with help of a dart board. Get back to the office, well, most of us are actually are going there for first time this week. We ship whatever code we get done by  5 pm. Never had any code problems.</p></htmltext>
<tokenext>F * * * You !
I right code for airplane fuel management systems and there is no need for review or even testing .
Design is almost non-existent , too .
Our design process goes as follows Late on Thursday with a Friday deadline .
We go out to our local bar for some drinks .
After , a bit of squabbling we right the requirement down on some napkins ; pick our programming language with help of a dart board .
Get back to the office , well , most of us are actually are going there for first time this week .
We ship whatever code we get done by 5 pm .
Never had any code problems .</tokentext>
<sentencetext>F*** You!
I right code for airplane fuel management systems and there is no need for review or even testing.
Design is almost non-existent, too.
Our design process goes as follows Late on Thursday with a Friday deadline.
We go out to our local bar for some drinks.
After, a bit of squabbling we right the requirement down on some napkins; pick our programming language with help of a dart board.
Get back to the office, well, most of us are actually are going there for first time this week.
We ship whatever code we get done by  5 pm.
Never had any code problems.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733291</id>
	<title>Swedish Nameservers Bork Bork Bork'd!</title>
	<author>Anonymous</author>
	<datestamp>1255455360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Film at Eleven.</p></htmltext>
<tokenext>Film at Eleven .</tokentext>
<sentencetext>Film at Eleven.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29742649</id>
	<title>Internet != web</title>
	<author>tequila13</author>
	<datestamp>1255520040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>From TFA: <p><div class="quote"><p>The entire Swedish Internet effectively stopped working at this point.</p></div><p>That's incorrect. Only domain lookups weren't working. The Internet was working fine.</p></div>
	</htmltext>
<tokenext>From TFA : The entire Swedish Internet effectively stopped working at this point.That 's incorrect .
Only domain lookups were n't working .
The Internet was working fine .</tokentext>
<sentencetext>From TFA: The entire Swedish Internet effectively stopped working at this point.That's incorrect.
Only domain lookups weren't working.
The Internet was working fine.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29739833</id>
	<title>Re:change control / management, anyone?</title>
	<author>Eil</author>
	<datestamp>1255443180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'm no DNS expert, but I can't fathom why negative responses are cached at all. You have many, many more requests for valid domains than you do for invalid ones and the vast majority of the invalid ones are one-off typos. I just don't see what the benefit is. We could do away with an entire class of sysadmin headaches if all resolver software configuration and network policies defaulted to not caching negative responses.</p></htmltext>
<tokenext>I 'm no DNS expert , but I ca n't fathom why negative responses are cached at all .
You have many , many more requests for valid domains than you do for invalid ones and the vast majority of the invalid ones are one-off typos .
I just do n't see what the benefit is .
We could do away with an entire class of sysadmin headaches if all resolver software configuration and network policies defaulted to not caching negative responses .</tokentext>
<sentencetext>I'm no DNS expert, but I can't fathom why negative responses are cached at all.
You have many, many more requests for valid domains than you do for invalid ones and the vast majority of the invalid ones are one-off typos.
I just don't see what the benefit is.
We could do away with an entire class of sysadmin headaches if all resolver software configuration and network policies defaulted to not caching negative responses.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734063</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733713</id>
	<title>Re:unless you are swedish</title>
	<author>medlefsen</author>
	<datestamp>1255457280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>What are you talking about?  Yes, for a single packet it's best effort, but you're ignoring all the other technologies and protocols that make up the internet.  Assuming there is *some* route to the destination and enough bandwidth to support the extra packets that come from resending large amounts of lost packets and the Internet will always work.  Don't confuse the low level architecture with the reliability of the entire infrastructure.

Of course, all of that is irrelevant to this particular problem because this wasn't a connection problem but a software configuration error.</htmltext>
<tokenext>What are you talking about ?
Yes , for a single packet it 's best effort , but you 're ignoring all the other technologies and protocols that make up the internet .
Assuming there is * some * route to the destination and enough bandwidth to support the extra packets that come from resending large amounts of lost packets and the Internet will always work .
Do n't confuse the low level architecture with the reliability of the entire infrastructure .
Of course , all of that is irrelevant to this particular problem because this was n't a connection problem but a software configuration error .</tokentext>
<sentencetext>What are you talking about?
Yes, for a single packet it's best effort, but you're ignoring all the other technologies and protocols that make up the internet.
Assuming there is *some* route to the destination and enough bandwidth to support the extra packets that come from resending large amounts of lost packets and the Internet will always work.
Don't confuse the low level architecture with the reliability of the entire infrastructure.
Of course, all of that is irrelevant to this particular problem because this wasn't a connection problem but a software configuration error.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733277</parent>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29739653
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_56</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733335
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733561
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735023
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_47</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734583
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_50</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733179
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733277
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733863
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734263
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735671
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_46</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733003
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733971
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735531
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733311
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734833
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733311
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734975
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733561
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29737389
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733179
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735621
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733003
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733971
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734871
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734165
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733311
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733623
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733179
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733277
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734611
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_59</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734543
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734133
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_62</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733179
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734383
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733975
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733597
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735527
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_54</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29742967
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734775
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733709
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_61</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734873
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734409
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_57</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733251
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733561
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734951
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_60</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733449
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_51</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734263
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734707
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733451
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733003
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733971
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29739549
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29738111
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_49</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29736007
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_52</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733667
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733621
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733093
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733201
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732877
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733361
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733179
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733351
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734093
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29739833
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733589
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29737071
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733467
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732987
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735803
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734615
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733417
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734495
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_55</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733999
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733179
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733277
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733713
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732903
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734765
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733111
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29739789
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733561
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734243
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732903
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735147
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732903
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735629
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_58</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733733
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29738171
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_63</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734651
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733997
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732877
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734825
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_48</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733093
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734859
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_53</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734451
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733465
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_10_13_1537207_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733739
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_13_1537207.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733499
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_13_1537207.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733315
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733449
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734133
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734495
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733999
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733975
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734583
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734165
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733451
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_13_1537207.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733093
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734859
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733201
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_13_1537207.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734263
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734707
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735671
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_13_1537207.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732877
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734825
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733361
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_13_1537207.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733733
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29738171
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_13_1537207.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733003
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733971
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29739549
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734871
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735531
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_13_1537207.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732903
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735147
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734765
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735629
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_13_1537207.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733063
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29739653
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733621
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733467
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733465
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734615
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733311
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733623
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734833
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735425
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29742967
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734063
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734409
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29736007
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29739833
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734975
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734451
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733709
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734543
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733597
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733667
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733589
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733335
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733997
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733251
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734651
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733739
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_10_13_1537207.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732895
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733417
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734775
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733111
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29739789
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29732987
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29737071
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29738111
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734873
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735527
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735803
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733179
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733351
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734383
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735621
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733277
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734611
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733863
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733713
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29733561
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734951
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734243
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29737389
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29735023
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_10_13_1537207.29734093
</commentlist>
</conversation>
