<?xml version="1.0" encoding="UTF-8"?><rss
version="2.0"
xmlns:content="http://purl.org/rss/1.0/modules/content/"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:atom="http://www.w3.org/2005/Atom"
xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
> <channel><title>Comments on: XName.org down: largest DDoS they ever had</title> <atom:link href="https://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html/feed" rel="self" type="application/rss+xml" /><link>https://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html</link> <description>Tiny bits of bioinformatics, [web-]programming etc</description> <lastBuildDate>Mon, 01 Jan 2024 17:12:20 +0000</lastBuildDate> <sy:updatePeriod>hourly</sy:updatePeriod> <sy:updateFrequency>1</sy:updateFrequency> <generator>https://wordpress.org/?v=3.8.27</generator> <item><title>By: Dinar Q.</title><link>https://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-112286</link> <dc:creator><![CDATA[Dinar Q.]]></dc:creator> <pubDate>Sun, 05 Sep 2010 07:27:30 +0000</pubDate> <guid
isPermaLink="false">http://www.bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-112286</guid> <description><![CDATA[it&#039;s now down again]]></description> <content:encoded><![CDATA[<p>it&#8217;s now down again</p> ]]></content:encoded> </item> <item><title>By: Xname is down again &#187; Autarchy of the Private Cave</title><link>https://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-69275</link> <dc:creator><![CDATA[Xname is down again &#187; Autarchy of the Private Cave]]></dc:creator> <pubDate>Sun, 25 May 2008 10:06:24 +0000</pubDate> <guid
isPermaLink="false">http://www.bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-69275</guid> <description><![CDATA[[...] XName is down again [...]]]></description> <content:encoded><![CDATA[<p>[...] XName is down again [...]</p> ]]></content:encoded> </item> <item><title>By: Bogdan</title><link>https://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-27601</link> <dc:creator><![CDATA[Bogdan]]></dc:creator> <pubDate>Wed, 10 Oct 2007 20:03:11 +0000</pubDate> <guid
isPermaLink="false">http://www.bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-27601</guid> <description><![CDATA[&lt;blockquote cite=&quot;xname-availability&quot;&gt;
Operations came back to normal at 12:00 AM today.
ns1 was up during the whole DDoS, and ns0 was off for all global access - but was accessible for our network peers.
To face these recurring problems, we&#039;ll set up shortly a third DNS server (under active testing at the moment), and we&#039;re studying how to build larger solutions accordingly with our resources (only from contributors). When done, announces will be done on xname-news mailing list.
&lt;/blockquote&gt;]]></description> <content:encoded><![CDATA[<blockquote
cite="xname-availability"><p> Operations came back to normal at 12:00 AM today.</p><p>ns1 was up during the whole DDoS, and ns0 was off for all global access &#8211; but was accessible for our network peers.</p><p>To face these recurring problems, we&#8217;ll set up shortly a third DNS server (under active testing at the moment), and we&#8217;re studying how to build larger solutions accordingly with our resources (only from contributors). When done, announces will be done on xname-news mailing list.</p></blockquote> ]]></content:encoded> </item> <item><title>By: Aidan</title><link>https://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-27497</link> <dc:creator><![CDATA[Aidan]]></dc:creator> <pubDate>Tue, 09 Oct 2007 21:55:03 +0000</pubDate> <guid
isPermaLink="false">http://www.bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-27497</guid> <description><![CDATA[&lt;blockquote cite=&quot;Bogdan&quot;&gt;Did you check manually, or have some (semi-)automatic means for checking?&lt;/blockquote&gt;
I&#039;m monitoring Ping responses from and DNS requests to ns0 and ns1 using &lt;a href=&quot;http://www.nagios.org/&quot; title=&quot;Nagios&quot; rel=&quot;nofollow&quot;&gt;Nagios&lt;/a&gt;.  I started doing this following the outage on the 1st.
I&#039;ve subscribed to the xname list but haven&#039;t had my e-mail yet so thanks for confirming the problem.
regards,
Aidan]]></description> <content:encoded><![CDATA[<blockquote
cite="Bogdan"><p>Did you check manually, or have some (semi-)automatic means for checking?</p></blockquote><p>I&#8217;m monitoring Ping responses from and DNS requests to ns0 and ns1 using <a
href="http://www.nagios.org/" title="Nagios" rel="nofollow">Nagios</a>.  I started doing this following the outage on the 1st.</p><p>I&#8217;ve subscribed to the xname list but haven&#8217;t had my e-mail yet so thanks for confirming the problem.</p><p>regards,<br
/> Aidan</p> ]]></content:encoded> </item> <item><title>By: Bogdan</title><link>https://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-27495</link> <dc:creator><![CDATA[Bogdan]]></dc:creator> <pubDate>Tue, 09 Oct 2007 21:33:22 +0000</pubDate> <guid
isPermaLink="false">http://www.bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-27495</guid> <description><![CDATA[Aidan,
thanks for sharing information. Did you check manually, or have some (semi-)automatic means for checking? I didn&#039;t notice any problems, but that is because I was too busy to have a look at my sites for several days in a row.
I must say though, that I did get an email. Here it is:
&lt;blockquote&gt;
Dear XName-Availability subscribers,
both ns0 and ns1 DNS servers are under heavy DDoS attack since 4:45 PM
(gmt+2) this afternoon.
The BGP session serving NS0 network is flapping due to a total
saturation of the link, so NS0 is up very intermittently.
ns1 is still online, even if loaded.
&lt;/blockquote&gt;
I got this email on the 9th of October at 23:00 gmt+2 from the XName-Availability mailing list.]]></description> <content:encoded><![CDATA[<p>Aidan,<br
/> thanks for sharing information. Did you check manually, or have some (semi-)automatic means for checking? I didn&#8217;t notice any problems, but that is because I was too busy to have a look at my sites for several days in a row.</p><p>I must say though, that I did get an email. Here it is:</p><blockquote><p> Dear XName-Availability subscribers,</p><p>both ns0 and ns1 DNS servers are under heavy DDoS attack since 4:45 PM<br
/> (gmt+2) this afternoon.</p><p>The BGP session serving NS0 network is flapping due to a total<br
/> saturation of the link, so NS0 is up very intermittently.</p><p>ns1 is still online, even if loaded.</p></blockquote><p>I got this email on the 9th of October at 23:00 gmt+2 from the XName-Availability mailing list.</p> ]]></content:encoded> </item> <item><title>By: Aidan</title><link>https://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-27464</link> <dc:creator><![CDATA[Aidan]]></dc:creator> <pubDate>Tue, 09 Oct 2007 18:00:01 +0000</pubDate> <guid
isPermaLink="false">http://www.bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-27464</guid> <description><![CDATA[&lt;strong&gt;Possible new attack on XName servers - 9 October 2007&lt;/strong&gt;
DNS resolution from ns0.xname.org was lost at 17:09 BST (16:09 GMT).  ICMP was lost at 16:05 BST.
ns1.xname.org is still resolving although ICMP has been intermittent since 16:59 BST.
I have not received any information from XName.  This is information I have gathered through my own monitoring.
HTH
Aidan]]></description> <content:encoded><![CDATA[<p><strong>Possible new attack on XName servers &#8211; 9 October 2007</strong></p><p>DNS resolution from ns0.xname.org was lost at 17:09 BST (16:09 GMT).  ICMP was lost at 16:05 BST.</p><p>ns1.xname.org is still resolving although ICMP has been intermittent since 16:59 BST.</p><p>I have not received any information from XName.  This is information I have gathered through my own monitoring.</p><p>HTH<br
/> Aidan</p> ]]></content:encoded> </item> <item><title>By: DNS troubles? &#187; Autarchy of the Private Cave</title><link>https://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-24155</link> <dc:creator><![CDATA[DNS troubles? &#187; Autarchy of the Private Cave]]></dc:creator> <pubDate>Mon, 01 Oct 2007 19:41:14 +0000</pubDate> <guid
isPermaLink="false">http://www.bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-24155</guid> <description><![CDATA[[...] Update: this is in fact XName-related problem: they are again under DDoS attack. [...]]]></description> <content:encoded><![CDATA[<p>[...] Update: this is in fact XName-related problem: they are again under DDoS attack. [...]</p> ]]></content:encoded> </item> <item><title>By: HTTP caching: universal approach and sample code &#187; Autarchy of the Private Cave</title><link>https://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-5068</link> <dc:creator><![CDATA[HTTP caching: universal approach and sample code &#187; Autarchy of the Private Cave]]></dc:creator> <pubDate>Thu, 03 May 2007 14:52:19 +0000</pubDate> <guid
isPermaLink="false">http://www.bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-5068</guid> <description><![CDATA[[...] Now, let&#039;s move on to actual caching. The simplest and quite reliable method of identifying any object within your cache is md5(url) - that is, the hash of the request URL. Note, that you might want to hash not the complete URL (starting with http://), but only the part after the TLD&#039;s slash, e.g. for complete URL http://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html you would hash only the &quot;xnameorg-down-largest-ddos-they-ever-had.html&quot; part (or &quot;2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html&quot;, if the filename part of the path might be non-unique). Evidently, this will save you from generating cache both for &quot;http://www.bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html&quot; and for &quot;http://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html&quot; (differing only in &quot;www.&quot; part). [...]]]></description> <content:encoded><![CDATA[<p>[...] Now, let&#8217;s move on to actual caching. The simplest and quite reliable method of identifying any object within your cache is md5(url) &#8211; that is, the hash of the request URL. Note, that you might want to hash not the complete URL (starting with <a
href="http://" rel="nofollow">http://</a>), but only the part after the TLD&#8217;s slash, e.g. for complete URL <a
href="http://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html" rel="nofollow">http://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html</a> you would hash only the &#8220;xnameorg-down-largest-ddos-they-ever-had.html&#8221; part (or &#8220;2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html&#8221;, if the filename part of the path might be non-unique). Evidently, this will save you from generating cache both for &#8220;http://www.bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html&#8221; and for &#8220;http://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html&#8221; (differing only in &#8220;www.&#8221; part). [...]</p> ]]></content:encoded> </item> <item><title>By: Ð’Ð°ÑÐ¸Ð»Ð¸Ð¹ Ð‘Ð¾Ñ€Ð¸ÑÐ¾Ð²Ð¸Ñ‡ Ð§ÐµÑ€ÑÐºÐ¸Ð¹</title><link>https://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-120</link> <dc:creator><![CDATA[Ð’Ð°ÑÐ¸Ð»Ð¸Ð¹ Ð‘Ð¾Ñ€Ð¸ÑÐ¾Ð²Ð¸Ñ‡ Ð§ÐµÑ€ÑÐºÐ¸Ð¹]]></dc:creator> <pubDate>Tue, 02 Jan 2007 18:26:20 +0000</pubDate> <guid
isPermaLink="false">http://www.bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-120</guid> <description><![CDATA[Ð½Ð° Ð¿Ñ€Ð¸Ð²Ð°Ñ‚Ð½Ð¸Ð¹ ÐºÐ°Ð½Ð°Ð» IRC Ð³Ð´Ðµ Ñ Ð±Ñ‹Ð²Ð°Ð», Ð° ÑÐ¾Ñ‚Ð¾Ð²Ð¾Ð¹ Ð°Ð´Ð¼Ð¸Ð½Ð¸Ñ‚Ñ€Ð°Ñ‚Ð¾Ñ€ ÑÐºÐ°Ð·Ð°Ð» :
Oct 27 06:14:29   xname : dead
Oct 27 06:15:09   DDoS depuis hier
Oct 27 06:15:20   dÃ¨s qu&#039;on essaye de remttre les NS up on se fait DDoS
Oct 27 06:16:21   UDP flood sur le port 53 des deux NS
Oct 27 06:16:46   donc clairement non filtrable
Oct 27 06:17:01   sur 10000 Ã  30000 ip sources diffÃ©rentes
Oct 27 06:32:55   bah mercredi on a eu un ddos sur xname en icmp type 0
Oct 27 06:33:04   ca a durÃ© 1h est c&#039;est passÃ©
Oct 27 06:33:05   la...
Oct 27 06:33:14   ca doit Ãªtre de putains de botnets de merde
Oct 27 06:33:20   qui nous casse les pieds
Oct 27 07:02:12   bon
Oct 27 07:02:13   y a un des connard qui emmerde xname qui est : 213.148.160.20
20.160.148.213.in-addr.arpa domain name pointer dc.natm.ru.
Oct 27 07:02:32   340352 packets en 5 minutes
Oct 27 07:03:39   Xname est down because DDoS depuis hier soir 19h
Oct 27 07:08:22   non en fait... je suis aussi l&#039;admin du reÃ©seau kheops qui herge kazar et xname
Oct 27 07:08:32   et ca c&#039;est  les traces netflow
Oct 27 07:08:40   # bgpctl sh ip bgp as 16301
Oct 27 07:08:40   flags: * = Valid, &gt; = Selected, I = via IBGP, A = Announced
Oct 27 07:08:40   origin: i = IGP, e = EGP, ? = Incomplete
Oct 27 07:08:40   flags destination         gateway          lpref   med aspath origin
Oct 27 07:08:40   *&gt;    84.242.192.0/18     213.163.173.46     100     0 20917 3257 25462 8997 16301 i
Oct 27 07:08:40   *&gt;    213.148.160.0/19    213.163.173.46     100     0 20917 3257 25462 8997 16301 i
Oct 27 07:08:49   vu qu&#039;ils ont deux subnet
Oct 27 07:09:00   je vais refuser toute annonce de l&#039;as16301
Oct 27 07:09:03   et on verra
Oct 27 11:29:45   vt: j&#039;ai 30Mbps qui vient de ces ips : 211.226.22.39, 219.138.151.156, 124.101.96.180, 58.70.87.229, 61.208.120.76, 219.134.185.188, 193.255.70.128, 70.83.237.133
Oct 27 11:50:09   Date flow start          Duration Proto      Src IP Addr:Port          Dst IP Addr:Port   Flags Tos  Packets    Bytes      pps      bps    Bpp Flows
Oct 27 11:50:09   2006-10-27 17:30:00.000   299.000 UDP      211.226.22.39:2344  -&gt;     195.234.42.1:53    ......   0   590592  333.7 M     1975    8.9 M    592  4614
Oct 27 11:50:10   2006-10-27 17:30:00.000   299.000 UDP    219.138.151.156:36082 -&gt;     195.234.42.1:53    .AP...   0   291200  165.8 M      973    4.4 M    597  2275
Ñ‚Ñ€Ð°Ñ„Ñ„Ð¸Ðº Ð½Ð° Ð³Ñ€Ð°Ñ„Ðµ (Ñƒ Ð¼ÐµÐ½Ñ Ð³Ñ€Ð°Ñ„ Ð½Ð° Ð´Ñ€ÑƒÐ³Ð¾Ð¼ ÐºÐ¾Ð¼Ð¿ÑŒÑŽÑ‚Ð¾Ñ€Ðµ - Ñ Ñ‚ÐµÐ±Ñ ÑÐ´Ð°ÑŽ) : 680 Mbit/s
Ð¯ Ð¾Ñ‚Ð¿Ñ€Ð°Ð²Ð¸Ð» E-mail Ð°Ð´Ð¼Ð¸Ð½Ð° natm.ru Ð¸ Ð¼Ð½Ðµ ÑÐºÐ°Ð·Ð°Ð»Ð¸ :
Â«
From: &quot;Sergey Goncharov&quot;
Subject: Re: DDoS na XName
Ð”Ð¾Ð±Ñ€Ñ‹Ð¹ Ð´ÐµÐ½ÑŒ, Ð’Ð°ÑÐ¸Ð»Ð¸Ð¹.
Ð”Ð°, Ð¼Ñ‹ Ð²
Ð˜ÑÑ‚Ð¾Ñ‡Ð½Ð¸Ðº ÑƒÐ¶Ðµ Ð»Ð¾ÐºÐ°Ð»Ð¸Ð·Ð¾Ð²Ð°Ð½.
ÐŸÑ€Ð¸Ð½Ð¾ÑÐ¸Ð¼ Ð¸Ð·Ð²Ð¸Ð½ÐµÐ½Ð¸Ñ Ð·Ð° Ð±ÐµÑÐ¿Ð¾ÐºÐ¾Ð¹ÑÑ‚Ð²Ð¾.
Ð¡ ÑƒÐ²Ð°Ð¶ÐµÐ½Ð¸ÐµÐ¼, Ð¡ÐµÑ€Ð³ÐµÐ¹ Ð“Ð¾Ð½Ñ‡Ð°Ñ€Ð¾Ð²
ÐžÐžÐž &quot;ÐÐ¾Ð²Ð³Ð¾Ñ€Ð¾Ð´ Ð”ÐµÐ¹Ñ‚Ð°ÐºÐ¾Ð¼&quot;, ÑÐ¸ÑÑ‚ÐµÐ¼Ð½Ñ‹Ð¹ Ð°Ð´Ð¼Ð¸Ð½Ð¸ÑÑ‚Ñ€Ð°Ñ‚Ð¾Ñ€
Â»]]></description> <content:encoded><![CDATA[<p>Ð½Ð° Ð¿Ñ€Ð¸Ð²Ð°Ñ‚Ð½Ð¸Ð¹ ÐºÐ°Ð½Ð°Ð» IRC Ð³Ð´Ðµ Ñ Ð±Ñ‹Ð²Ð°Ð», Ð° ÑÐ¾Ñ‚Ð¾Ð²Ð¾Ð¹ Ð°Ð´Ð¼Ð¸Ð½Ð¸Ñ‚Ñ€Ð°Ñ‚Ð¾Ñ€ ÑÐºÐ°Ð·Ð°Ð» :</p><p>Oct 27 06:14:29   xname : dead<br
/> Oct 27 06:15:09   DDoS depuis hier<br
/> Oct 27 06:15:20   dÃ¨s qu&#8217;on essaye de remttre les NS up on se fait DDoS<br
/> Oct 27 06:16:21   UDP flood sur le port 53 des deux NS<br
/> Oct 27 06:16:46   donc clairement non filtrable<br
/> Oct 27 06:17:01   sur 10000 Ã  30000 ip sources diffÃ©rentes<br
/> Oct 27 06:32:55   bah mercredi on a eu un ddos sur xname en icmp type 0<br
/> Oct 27 06:33:04   ca a durÃ© 1h est c&#8217;est passÃ©<br
/> Oct 27 06:33:05   la&#8230;<br
/> Oct 27 06:33:14   ca doit Ãªtre de putains de botnets de merde<br
/> Oct 27 06:33:20   qui nous casse les pieds<br
/> Oct 27 07:02:12   bon<br
/> Oct 27 07:02:13   y a un des connard qui emmerde xname qui est : 213.148.160.20</p><p>20.160.148.213.in-addr.arpa domain name pointer dc.natm.ru.</p><p>Oct 27 07:02:32   340352 packets en 5 minutes<br
/> Oct 27 07:03:39   Xname est down because DDoS depuis hier soir 19h<br
/> Oct 27 07:08:22   non en fait&#8230; je suis aussi l&#8217;admin du reÃ©seau kheops qui herge kazar et xname<br
/> Oct 27 07:08:32   et ca c&#8217;est  les traces netflow<br
/> Oct 27 07:08:40   # bgpctl sh ip bgp as 16301<br
/> Oct 27 07:08:40   flags: * = Valid, &gt; = Selected, I = via IBGP, A = Announced<br
/> Oct 27 07:08:40   origin: i = IGP, e = EGP, ? = Incomplete<br
/> Oct 27 07:08:40   flags destination         gateway          lpref   med aspath origin<br
/> Oct 27 07:08:40   *&gt;    84.242.192.0/18     213.163.173.46     100     0 20917 3257 25462 8997 16301 i<br
/> Oct 27 07:08:40   *&gt;    213.148.160.0/19    213.163.173.46     100     0 20917 3257 25462 8997 16301 i<br
/> Oct 27 07:08:49   vu qu&#8217;ils ont deux subnet<br
/> Oct 27 07:09:00   je vais refuser toute annonce de l&#8217;as16301<br
/> Oct 27 07:09:03   et on verra<br
/> Oct 27 11:29:45   vt: j&#8217;ai 30Mbps qui vient de ces ips : 211.226.22.39, 219.138.151.156, 124.101.96.180, 58.70.87.229, 61.208.120.76, 219.134.185.188, 193.255.70.128, 70.83.237.133<br
/> Oct 27 11:50:09   Date flow start          Duration Proto      Src IP Addr:Port          Dst IP Addr:Port   Flags Tos  Packets    Bytes      pps      bps    Bpp Flows<br
/> Oct 27 11:50:09   2006-10-27 17:30:00.000   299.000 UDP      211.226.22.39:2344  -&gt;     195.234.42.1:53    &#8230;&#8230;   0   590592  333.7 M     1975    8.9 M    592  4614<br
/> Oct 27 11:50:10   2006-10-27 17:30:00.000   299.000 UDP    219.138.151.156:36082 -&gt;     195.234.42.1:53    .AP&#8230;   0   291200  165.8 M      973    4.4 M    597  2275</p><p>Ñ‚Ñ€Ð°Ñ„Ñ„Ð¸Ðº Ð½Ð° Ð³Ñ€Ð°Ñ„Ðµ (Ñƒ Ð¼ÐµÐ½Ñ Ð³Ñ€Ð°Ñ„ Ð½Ð° Ð´Ñ€ÑƒÐ³Ð¾Ð¼ ÐºÐ¾Ð¼Ð¿ÑŒÑŽÑ‚Ð¾Ñ€Ðµ &#8211; Ñ Ñ‚ÐµÐ±Ñ ÑÐ´Ð°ÑŽ) : 680 Mbit/s</p><p>Ð¯ Ð¾Ñ‚Ð¿Ñ€Ð°Ð²Ð¸Ð» E-mail Ð°Ð´Ð¼Ð¸Ð½Ð° natm.ru Ð¸ Ð¼Ð½Ðµ ÑÐºÐ°Ð·Ð°Ð»Ð¸ :<br
/> Â«<br
/> From: &#8220;Sergey Goncharov&#8221;<br
/> Subject: Re: DDoS na XName</p><p>Ð”Ð¾Ð±Ñ€Ñ‹Ð¹ Ð´ÐµÐ½ÑŒ, Ð’Ð°ÑÐ¸Ð»Ð¸Ð¹.</p><p>Ð”Ð°, Ð¼Ñ‹ Ð²<br
/> Ð˜ÑÑ‚Ð¾Ñ‡Ð½Ð¸Ðº ÑƒÐ¶Ðµ Ð»Ð¾ÐºÐ°Ð»Ð¸Ð·Ð¾Ð²Ð°Ð½.</p><p>ÐŸÑ€Ð¸Ð½Ð¾ÑÐ¸Ð¼ Ð¸Ð·Ð²Ð¸Ð½ÐµÐ½Ð¸Ñ Ð·Ð° Ð±ÐµÑÐ¿Ð¾ÐºÐ¾Ð¹ÑÑ‚Ð²Ð¾.</p><p>Ð¡ ÑƒÐ²Ð°Ð¶ÐµÐ½Ð¸ÐµÐ¼, Ð¡ÐµÑ€Ð³ÐµÐ¹ Ð“Ð¾Ð½Ñ‡Ð°Ñ€Ð¾Ð²<br
/> ÐžÐžÐž &#8220;ÐÐ¾Ð²Ð³Ð¾Ñ€Ð¾Ð´ Ð”ÐµÐ¹Ñ‚Ð°ÐºÐ¾Ð¼&#8221;, ÑÐ¸ÑÑ‚ÐµÐ¼Ð½Ñ‹Ð¹ Ð°Ð´Ð¼Ð¸Ð½Ð¸ÑÑ‚Ñ€Ð°Ñ‚Ð¾Ñ€<br
/> Â»</p> ]]></content:encoded> </item> <item><title>By: chronos</title><link>https://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-119</link> <dc:creator><![CDATA[chronos]]></dc:creator> <pubDate>Tue, 02 Jan 2007 10:44:32 +0000</pubDate> <guid
isPermaLink="false">http://www.bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-119</guid> <description><![CDATA[Ð Ð³Ð´Ðµ Ð¾Ð± ÑÑ‚Ð¾Ð¼ ÑÐ¾Ð¾Ð±Ñ‰Ð°Ð»Ð¸? Ð¯ Ð±Ñ‹ Ð´Ð¾Ð±Ð°Ð²Ð¸Ð» ÑÑŽÐ´Ð° Ð¿Ð¾Ð´Ñ€Ð¾Ð±Ð½Ð¾ÑÑ‚Ð¸...]]></description> <content:encoded><![CDATA[<p>Ð Ð³Ð´Ðµ Ð¾Ð± ÑÑ‚Ð¾Ð¼ ÑÐ¾Ð¾Ð±Ñ‰Ð°Ð»Ð¸? Ð¯ Ð±Ñ‹ Ð´Ð¾Ð±Ð°Ð²Ð¸Ð» ÑÑŽÐ´Ð° Ð¿Ð¾Ð´Ñ€Ð¾Ð±Ð½Ð¾ÑÑ‚Ð¸&#8230;</p> ]]></content:encoded> </item> <item><title>By: Ð’Ð°ÑÐ¸Ð»Ð¸Ð¹ Ð‘Ð¾Ñ€Ð¸ÑÐ¾Ð²Ð¸Ñ‡ Ð§ÐµÑ€ÑÐºÐ¸Ð¹</title><link>https://bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-118</link> <dc:creator><![CDATA[Ð’Ð°ÑÐ¸Ð»Ð¸Ð¹ Ð‘Ð¾Ñ€Ð¸ÑÐ¾Ð²Ð¸Ñ‡ Ð§ÐµÑ€ÑÐºÐ¸Ð¹]]></dc:creator> <pubDate>Mon, 01 Jan 2007 23:32:36 +0000</pubDate> <guid
isPermaLink="false">http://www.bogdan.org.ua/2006/10/27/xnameorg-down-largest-ddos-they-ever-had.html#comment-118</guid> <description><![CDATA[ÐšÑÑ‚Ð°Ñ‚Ð¸, Ð¾Ð½Ð¸ Ñ„Ð»ÑƒÐ´Ð¸Ñ€Ð¾Ð²Ð°Ð»Ð¸ Xname Ð¸Ð· Ñ€Ð¾ÑÑÐ¸Ð¹ÑÐºÐ¾Ð¹ ISP Ð² ÐšÑ€Ð°ÑÐ½Ð¾ÑÑ€ÑÐºÐµ :/]]></description> <content:encoded><![CDATA[<p>ÐšÑÑ‚Ð°Ñ‚Ð¸, Ð¾Ð½Ð¸ Ñ„Ð»ÑƒÐ´Ð¸Ñ€Ð¾Ð²Ð°Ð»Ð¸ Xname Ð¸Ð· Ñ€Ð¾ÑÑÐ¸Ð¹ÑÐºÐ¾Ð¹ ISP Ð² ÐšÑ€Ð°ÑÐ½Ð¾ÑÑ€ÑÐºÐµ :/</p> ]]></content:encoded> </item> </channel> </rss>