<?xml version="1.0" encoding="UTF-8"?>

<rss version="2.0" xmlns:blogChannel="http://backend.userland.com/blogChannelModule">

<channel>
<title>DNS servers in </title>
<link>http://www.dslreports.com/forum/r10537692</link>
<description></description>
<language>en</language>
<pubDate>Fri, 27 Nov 2009 16:14:37 EDT</pubDate>
<lastBuildDate>Fri, 27 Nov 2009 16:14:37 EDT</lastBuildDate>

<item>
<title>Re: DNS servers</title>
<link>http://www.dslreports.com/forum/remark,10540281</link>
<description><![CDATA[<A HREF="/useremail/u/304237"><b>keith2468</b></A> : Comcast uses Yahoo DNS servers?  <br><br>Doesn't Comcast have its own?<br><br>Wouldn't they only be referring to the Yahoo ones when their last resolution of Yahoo domains had expired?]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10540281</guid>
<pubDate>Thu, 17 Jun 2004 22:18:26 EDT</pubDate>
</item>

<item>
<title>DNS servers</title>
<link>http://www.dslreports.com/forum/remark,10537692</link>
<description><![CDATA[<A HREF="/useremail/u/432210"><b>fractalspher</b></A> : This particular attack actually effected me!<br><br>Our public DNS server is (we now know) part of the Yahoo DNS servers.  So at 7:am that morning I got a bunch of DNS alerts on my cellphone and in emails for servers on the west coast.  I thought there had been an earthquake in San Francisco!  :p<br><br>  Ultimately it didn't kill our service, but did manage to give us about 100 DNS timeout errors all morning.  :mad:<br><br>As for the actual attack, they seemed to get it shut down fairly quickly...   Less than a few hours.<br><br>Also, this was the day my yahoo email account was getting upgraded and I couldn't get email all morning either!  :huh:<br><SMALL>--<br>FractalSphere - "Maybe it's in the basement, I'll go upstairs and check" - M.C. Escher</SMALL>]]></description>
<guid isPermaLink="true">http://www.dslreports.com/forum/remark,10537692</guid>
<pubDate>Thu, 17 Jun 2004 17:21:34 EDT</pubDate>
</item>

</channel>
</rss>
