<article>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#article09_06_09_1731238</id>
	<title>Comcast Intercepts and Redirects Port 53 Traffic</title>
	<author>kdawson</author>
	<datestamp>1244571060000</datestamp>
	<htmltext>An anonymous reader writes <i>"An interesting (and profane) writeup of one frustrated user's discovery that Comcast is actually <a href="http://comcastisfuckingwithyourport53traffic.wordpress.com/">intercepting DNS requests bound for non-Comcast DNS servers</a> and redirecting them to their own servers. I had obviously heard of the DNS hijacking for nonexistent domains, but I had no idea they'd actually prevent people from directly contacting their own DNS servers."</i> If true, this is a pretty serious escalation in the Net Neutrality wars. Someone using Comcast, please replicate the simple experiment spelled out in the article and confirm or deny the truth of it. Also, it would be useful if someone using Comcast ran the <a href="http://netalyzr.icsi.berkeley.edu/">ICSI Netalyzr</a> and posted the resulting permalink in the comments.</htmltext>
<tokenext>An anonymous reader writes " An interesting ( and profane ) writeup of one frustrated user 's discovery that Comcast is actually intercepting DNS requests bound for non-Comcast DNS servers and redirecting them to their own servers .
I had obviously heard of the DNS hijacking for nonexistent domains , but I had no idea they 'd actually prevent people from directly contacting their own DNS servers .
" If true , this is a pretty serious escalation in the Net Neutrality wars .
Someone using Comcast , please replicate the simple experiment spelled out in the article and confirm or deny the truth of it .
Also , it would be useful if someone using Comcast ran the ICSI Netalyzr and posted the resulting permalink in the comments .</tokentext>
<sentencetext>An anonymous reader writes "An interesting (and profane) writeup of one frustrated user's discovery that Comcast is actually intercepting DNS requests bound for non-Comcast DNS servers and redirecting them to their own servers.
I had obviously heard of the DNS hijacking for nonexistent domains, but I had no idea they'd actually prevent people from directly contacting their own DNS servers.
" If true, this is a pretty serious escalation in the Net Neutrality wars.
Someone using Comcast, please replicate the simple experiment spelled out in the article and confirm or deny the truth of it.
Also, it would be useful if someone using Comcast ran the ICSI Netalyzr and posted the resulting permalink in the comments.</sentencetext>
</article>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270021</id>
	<title>FIOS VERIZON did this to me too...</title>
	<author>Anonymous</author>
	<datestamp>1244578500000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I had to put a different Verizon DNS into the Router to get them to stop hijacking my DNS.  I was having VPN issues and issues with stuff running as <a href="http://localhost/" title="localhost" rel="nofollow">http://localhost/</a> [localhost] and then it got my attention...

They all seem to monitor as much as they can, Seems like ISP = iSPY4NSA!!!</htmltext>
<tokenext>I had to put a different Verizon DNS into the Router to get them to stop hijacking my DNS .
I was having VPN issues and issues with stuff running as http : //localhost/ [ localhost ] and then it got my attention.. . They all seem to monitor as much as they can , Seems like ISP = iSPY4NSA ! !
!</tokentext>
<sentencetext>I had to put a different Verizon DNS into the Router to get them to stop hijacking my DNS.
I was having VPN issues and issues with stuff running as http://localhost/ [localhost] and then it got my attention...

They all seem to monitor as much as they can, Seems like ISP = iSPY4NSA!!
!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28276961</id>
	<title>want free inet from comcast?</title>
	<author>luciferxe</author>
	<datestamp>1244629080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>goto a store. buy a cable modem. plug it into your comcast line. change your dns manually.

your done free inet from comcast i believe the speeds are 5/1mbit or something along those lines but its free. with a bit of modem modification you can uncap your modem completely.</htmltext>
<tokenext>goto a store .
buy a cable modem .
plug it into your comcast line .
change your dns manually .
your done free inet from comcast i believe the speeds are 5/1mbit or something along those lines but its free .
with a bit of modem modification you can uncap your modem completely .</tokentext>
<sentencetext>goto a store.
buy a cable modem.
plug it into your comcast line.
change your dns manually.
your done free inet from comcast i believe the speeds are 5/1mbit or something along those lines but its free.
with a bit of modem modification you can uncap your modem completely.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275617</id>
	<title>Use wikipedia?</title>
	<author>TheDreadedGMan</author>
	<datestamp>1244571480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>A quick search of information on Earthlink returned this:</p><p><a href="http://en.wikipedia.org/wiki/Earthlink#DNS\_and\_filtering\_controversy" title="wikipedia.org" rel="nofollow">http://en.wikipedia.org/wiki/Earthlink#DNS\_and\_filtering\_controversy</a> [wikipedia.org]</p><p>Which links to a page with DNS servers that are unsupported and unfiltered... might pay for anyone affected to at least try them.</p></htmltext>
<tokenext>A quick search of information on Earthlink returned this : http : //en.wikipedia.org/wiki/Earthlink # DNS \ _and \ _filtering \ _controversy [ wikipedia.org ] Which links to a page with DNS servers that are unsupported and unfiltered... might pay for anyone affected to at least try them .</tokentext>
<sentencetext>A quick search of information on Earthlink returned this:http://en.wikipedia.org/wiki/Earthlink#DNS\_and\_filtering\_controversy [wikipedia.org]Which links to a page with DNS servers that are unsupported and unfiltered... might pay for anyone affected to at least try them.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270121</id>
	<title>Cannot verify this report</title>
	<author>kheldan</author>
	<datestamp>1244578860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Conducted my own test based on how OpenDNS works. Changed my DNS server settings to OpenDNS (208.67.222.222 and 208.67.220.220) then tried to browse to a non-existent web page (http://comcast.sucks.com). Since it doesn't exist, I got the OpenDNS Guide search results page instead of a 404 or some other generic error. Unless someone can poke holes in this method, this pretty clearly indicates to me that Comcast is not doing anything sketchy with DNS requests, at least not in my geographic location (Sacramento, California); as always, your mileage may vary.</htmltext>
<tokenext>Conducted my own test based on how OpenDNS works .
Changed my DNS server settings to OpenDNS ( 208.67.222.222 and 208.67.220.220 ) then tried to browse to a non-existent web page ( http : //comcast.sucks.com ) .
Since it does n't exist , I got the OpenDNS Guide search results page instead of a 404 or some other generic error .
Unless someone can poke holes in this method , this pretty clearly indicates to me that Comcast is not doing anything sketchy with DNS requests , at least not in my geographic location ( Sacramento , California ) ; as always , your mileage may vary .</tokentext>
<sentencetext>Conducted my own test based on how OpenDNS works.
Changed my DNS server settings to OpenDNS (208.67.222.222 and 208.67.220.220) then tried to browse to a non-existent web page (http://comcast.sucks.com).
Since it doesn't exist, I got the OpenDNS Guide search results page instead of a 404 or some other generic error.
Unless someone can poke holes in this method, this pretty clearly indicates to me that Comcast is not doing anything sketchy with DNS requests, at least not in my geographic location (Sacramento, California); as always, your mileage may vary.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270405</id>
	<title>Earthlink here</title>
	<author>CSFFlame</author>
	<datestamp>1244579880000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>My DSL line is physically leased by earthlink from covad.  I use opendns, no redirection away from opendns.</htmltext>
<tokenext>My DSL line is physically leased by earthlink from covad .
I use opendns , no redirection away from opendns .</tokentext>
<sentencetext>My DSL line is physically leased by earthlink from covad.
I use opendns, no redirection away from opendns.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272305</id>
	<title>Comcast hates VA?</title>
	<author>Cleeq</author>
	<datestamp>1244545320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>c-76-123-201-223.hsd1.va.comcast.net / 76.123.xxx.xxx

Your global IP address is 76.123.xx.xx while your local one is 192.168.xx.xx You are behind a NAT. Your local address is in unroutable address space.

Your NAT renumbers TCP source ports sequentially. The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis.

port sequence plot

DNS-based host information: OK
You are not a Tor exit node for HTTP traffic.
You are listed on the Spamhaus Policy Based Blacklist, meaning that your provider has designated your address block as one that should not be sending any email.
The SORBS DUHL believes you are using a dynamically assigned IP address.
Reachability Tests

General connectivity: Note
Basic UDP access is available.
Direct UDP access to remote DNS servers (port 53) is blocked.
The network you are using appears to enforce the use of a local DNS resolver.
Direct UDP access to remote MSSQL servers (port 1434) is blocked.
This is most likely due to a filtering rule against the Slammer worm.
Direct TCP access to remote FTP servers (port 21) is allowed.
Direct TCP access to remote SSH servers (port 22) is allowed.
Direct TCP access to remote SMTP servers (port 25) is allowed.
Direct TCP access to remote DNS servers (port 53) is allowed.
Direct TCP access to remote HTTP servers (port 80) is allowed.
Direct TCP access to remote POP servers (port 110) is allowed.
Direct TCP access to remote RPC servers (port 135) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote NetBIOS servers (port 139) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote IMAP servers (port 143) is allowed.
Direct TCP access to remote SNMP servers (port 161) is allowed.
Direct TCP access to remote HTTPS servers (port 443) is allowed.
Direct TCP access to remote SMB servers (port 445) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.
Direct TCP access to remote secure IMAP servers (port 585) is allowed.
Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.
Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.
Direct TCP access to remote POP/SSL servers (port 995) is allowed.
Direct TCP access to remote SIP servers (port 5060) is allowed.
Direct TCP access to remote BitTorrent servers (port 6881) is allowed.</htmltext>
<tokenext>c-76-123-201-223.hsd1.va.comcast.net / 76.123.xxx.xxx Your global IP address is 76.123.xx.xx while your local one is 192.168.xx.xx You are behind a NAT .
Your local address is in unroutable address space .
Your NAT renumbers TCP source ports sequentially .
The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis .
port sequence plot DNS-based host information : OK You are not a Tor exit node for HTTP traffic .
You are listed on the Spamhaus Policy Based Blacklist , meaning that your provider has designated your address block as one that should not be sending any email .
The SORBS DUHL believes you are using a dynamically assigned IP address .
Reachability Tests General connectivity : Note Basic UDP access is available .
Direct UDP access to remote DNS servers ( port 53 ) is blocked .
The network you are using appears to enforce the use of a local DNS resolver .
Direct UDP access to remote MSSQL servers ( port 1434 ) is blocked .
This is most likely due to a filtering rule against the Slammer worm .
Direct TCP access to remote FTP servers ( port 21 ) is allowed .
Direct TCP access to remote SSH servers ( port 22 ) is allowed .
Direct TCP access to remote SMTP servers ( port 25 ) is allowed .
Direct TCP access to remote DNS servers ( port 53 ) is allowed .
Direct TCP access to remote HTTP servers ( port 80 ) is allowed .
Direct TCP access to remote POP servers ( port 110 ) is allowed .
Direct TCP access to remote RPC servers ( port 135 ) is blocked .
This is probably for security reasons , as this protocol is generally not designed for use outside the local network .
Direct TCP access to remote NetBIOS servers ( port 139 ) is blocked .
This is probably for security reasons , as this protocol is generally not designed for use outside the local network .
Direct TCP access to remote IMAP servers ( port 143 ) is allowed .
Direct TCP access to remote SNMP servers ( port 161 ) is allowed .
Direct TCP access to remote HTTPS servers ( port 443 ) is allowed .
Direct TCP access to remote SMB servers ( port 445 ) is blocked .
This is probably for security reasons , as this protocol is generally not designed for use outside the local network .
Direct TCP access to remote SMTP/SSL servers ( port 465 ) is allowed .
Direct TCP access to remote secure IMAP servers ( port 585 ) is allowed .
Direct TCP access to remote authenticated SMTP servers ( port 587 ) is allowed .
Direct TCP access to remote IMAP/SSL servers ( port 993 ) is allowed .
Direct TCP access to remote POP/SSL servers ( port 995 ) is allowed .
Direct TCP access to remote SIP servers ( port 5060 ) is allowed .
Direct TCP access to remote BitTorrent servers ( port 6881 ) is allowed .</tokentext>
<sentencetext>c-76-123-201-223.hsd1.va.comcast.net / 76.123.xxx.xxx

Your global IP address is 76.123.xx.xx while your local one is 192.168.xx.xx You are behind a NAT.
Your local address is in unroutable address space.
Your NAT renumbers TCP source ports sequentially.
The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis.
port sequence plot

DNS-based host information: OK
You are not a Tor exit node for HTTP traffic.
You are listed on the Spamhaus Policy Based Blacklist, meaning that your provider has designated your address block as one that should not be sending any email.
The SORBS DUHL believes you are using a dynamically assigned IP address.
Reachability Tests

General connectivity: Note
Basic UDP access is available.
Direct UDP access to remote DNS servers (port 53) is blocked.
The network you are using appears to enforce the use of a local DNS resolver.
Direct UDP access to remote MSSQL servers (port 1434) is blocked.
This is most likely due to a filtering rule against the Slammer worm.
Direct TCP access to remote FTP servers (port 21) is allowed.
Direct TCP access to remote SSH servers (port 22) is allowed.
Direct TCP access to remote SMTP servers (port 25) is allowed.
Direct TCP access to remote DNS servers (port 53) is allowed.
Direct TCP access to remote HTTP servers (port 80) is allowed.
Direct TCP access to remote POP servers (port 110) is allowed.
Direct TCP access to remote RPC servers (port 135) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote NetBIOS servers (port 139) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote IMAP servers (port 143) is allowed.
Direct TCP access to remote SNMP servers (port 161) is allowed.
Direct TCP access to remote HTTPS servers (port 443) is allowed.
Direct TCP access to remote SMB servers (port 445) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.
Direct TCP access to remote secure IMAP servers (port 585) is allowed.
Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.
Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.
Direct TCP access to remote POP/SSL servers (port 995) is allowed.
Direct TCP access to remote SIP servers (port 5060) is allowed.
Direct TCP access to remote BitTorrent servers (port 6881) is allowed.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270791</id>
	<title>Not happening in Mountain View, CA</title>
	<author>Anonymous</author>
	<datestamp>1244538360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><a href="http://koitsu.wordpress.com/2009/06/09/comcast-isnt-messing-with-my-port-53-traffic/" title="wordpress.com" rel="nofollow">http://koitsu.wordpress.com/2009/06/09/comcast-isnt-messing-with-my-port-53-traffic/</a> [wordpress.com]</p></htmltext>
<tokenext>http : //koitsu.wordpress.com/2009/06/09/comcast-isnt-messing-with-my-port-53-traffic/ [ wordpress.com ]</tokentext>
<sentencetext>http://koitsu.wordpress.com/2009/06/09/comcast-isnt-messing-with-my-port-53-traffic/ [wordpress.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269793</id>
	<title>lack of competition</title>
	<author>Anonymous</author>
	<datestamp>1244577480000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>The more the big guys push the small guys out of business, the more this kind of crap is going to happen...</p></htmltext>
<tokenext>The more the big guys push the small guys out of business , the more this kind of crap is going to happen.. .</tokentext>
<sentencetext>The more the big guys push the small guys out of business, the more this kind of crap is going to happen...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091</id>
	<title>Fuck `Em All</title>
	<author>Anonymous</author>
	<datestamp>1244575080000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext><p>When Comcast took over from Time Warner here, I bailed.</p><p>I mean, Time Warner is evil.  AT&amp;T (who I switched to), is evil.</p><p>But Comcast is Motherfucking Sith Lord EVIL.</p><p>Scary fucking eeeeevil.  Nazi evil.  RIAA evil.</p><p>
&nbsp;</p></htmltext>
<tokenext>When Comcast took over from Time Warner here , I bailed.I mean , Time Warner is evil .
AT&amp;T ( who I switched to ) , is evil.But Comcast is Motherfucking Sith Lord EVIL.Scary fucking eeeeevil .
Nazi evil .
RIAA evil .
 </tokentext>
<sentencetext>When Comcast took over from Time Warner here, I bailed.I mean, Time Warner is evil.
AT&amp;T (who I switched to), is evil.But Comcast is Motherfucking Sith Lord EVIL.Scary fucking eeeeevil.
Nazi evil.
RIAA evil.
 </sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269999</id>
	<title>Re:Port 53 Rerouted in Seattle :|</title>
	<author>nweaver</author>
	<datestamp>1244578440000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p>Your netalyzr results show no DNS issues in the link you posted, using a Comcast DNS server:</p><blockquote><div><p>c-24-22-147-111.hsd1.wa.comcast.net / 24.22.147.111</p></div></blockquote><blockquote><div><p>Direct UDP access to remote DNS servers (port 53) is allowed.<br>The applet was also able to directly request a large DNS response.</p></div></blockquote><blockquote><div><p>The IP address of your ISP's DNS Resolver is 68.87.69.147,<br>which resolves to bvrt-cns01.beaverton.or.bverton.comcast.net.</p></div></blockquote><blockquote><div><p>Your ISP correctly leaves non-resolving names untouched.</p></div></blockquote></div>
	</htmltext>
<tokenext>Your netalyzr results show no DNS issues in the link you posted , using a Comcast DNS server : c-24-22-147-111.hsd1.wa.comcast.net / 24.22.147.111Direct UDP access to remote DNS servers ( port 53 ) is allowed.The applet was also able to directly request a large DNS response.The IP address of your ISP 's DNS Resolver is 68.87.69.147,which resolves to bvrt-cns01.beaverton.or.bverton.comcast.net.Your ISP correctly leaves non-resolving names untouched .</tokentext>
<sentencetext>Your netalyzr results show no DNS issues in the link you posted, using a Comcast DNS server:c-24-22-147-111.hsd1.wa.comcast.net / 24.22.147.111Direct UDP access to remote DNS servers (port 53) is allowed.The applet was also able to directly request a large DNS response.The IP address of your ISP's DNS Resolver is 68.87.69.147,which resolves to bvrt-cns01.beaverton.or.bverton.comcast.net.Your ISP correctly leaves non-resolving names untouched.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269633</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270483</id>
	<title>Re:Comcast results in Houston, TX</title>
	<author>EvilBudMan</author>
	<datestamp>1244580180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I think you have to test with a static IP. You are behind NAT so I don't think you are going to be running a web server. I think what has happened is that someone like me with a static IP run the test, but I forgot, we are not running a web server, so it couldn't get through. The applet got through the firewall and hit a dead end. No one else is getting it blocked pretty much so I'm suspicious about it.</p><p>BTW, I would post a link to my IP address on<nobr> <wbr></nobr>/. I would cut n paste and leave the vitals out of it.</p></htmltext>
<tokenext>I think you have to test with a static IP .
You are behind NAT so I do n't think you are going to be running a web server .
I think what has happened is that someone like me with a static IP run the test , but I forgot , we are not running a web server , so it could n't get through .
The applet got through the firewall and hit a dead end .
No one else is getting it blocked pretty much so I 'm suspicious about it.BTW , I would post a link to my IP address on / .
I would cut n paste and leave the vitals out of it .</tokentext>
<sentencetext>I think you have to test with a static IP.
You are behind NAT so I don't think you are going to be running a web server.
I think what has happened is that someone like me with a static IP run the test, but I forgot, we are not running a web server, so it couldn't get through.
The applet got through the firewall and hit a dead end.
No one else is getting it blocked pretty much so I'm suspicious about it.BTW, I would post a link to my IP address on /.
I would cut n paste and leave the vitals out of it.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269269</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273845</id>
	<title>Re:Is this happening for ANYONE?</title>
	<author>jonaskoelker</author>
	<datestamp>1244556300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Toyota tracking all US drivers with a device hidden in the glove box!</p></div><p>They must be terrorists!  Only terrorists would monitor a whole population.  You should go over and fight them over there, so you don't have to fight them at home.</p><p>Uhmm... or something...</p></div>
	</htmltext>
<tokenext>Toyota tracking all US drivers with a device hidden in the glove box ! They must be terrorists !
Only terrorists would monitor a whole population .
You should go over and fight them over there , so you do n't have to fight them at home.Uhmm... or something.. .</tokentext>
<sentencetext>Toyota tracking all US drivers with a device hidden in the glove box!They must be terrorists!
Only terrorists would monitor a whole population.
You should go over and fight them over there, so you don't have to fight them at home.Uhmm... or something...
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269435</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273923</id>
	<title>Re:Fuck `Em All</title>
	<author>FireFly9</author>
	<datestamp>1244556900000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Oh, that was funny! I was crying!!! So fucking true!</htmltext>
<tokenext>Oh , that was funny !
I was crying ! ! !
So fucking true !</tokentext>
<sentencetext>Oh, that was funny!
I was crying!!!
So fucking true!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269251</id>
	<title>Re:Not happening to me</title>
	<author>CodeBuster</author>
	<datestamp>1244575560000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext>Are you certain? If they are redirecting the traffic in their network so that one of their DNS servers responds to the query <i> <b>as if</b> </i> it was your DNS server (i.e. forging the response packets so that they appear to come from your server) then the only way to tell would be to place a deliberately wrong IP entry for a well known address on your server (i.e. something that Comcast wouldn't know about) and then run the query again to see if you get the wrong result (no redirection or impersonation) OR if you get the expected result (redirection or impersonation). Also, they might only be forwarding queries that they don't recognize to your server so that any custom or unusual queries hit your server but stuff like google.com is answered by their server(s).</htmltext>
<tokenext>Are you certain ?
If they are redirecting the traffic in their network so that one of their DNS servers responds to the query as if it was your DNS server ( i.e .
forging the response packets so that they appear to come from your server ) then the only way to tell would be to place a deliberately wrong IP entry for a well known address on your server ( i.e .
something that Comcast would n't know about ) and then run the query again to see if you get the wrong result ( no redirection or impersonation ) OR if you get the expected result ( redirection or impersonation ) .
Also , they might only be forwarding queries that they do n't recognize to your server so that any custom or unusual queries hit your server but stuff like google.com is answered by their server ( s ) .</tokentext>
<sentencetext>Are you certain?
If they are redirecting the traffic in their network so that one of their DNS servers responds to the query  as if  it was your DNS server (i.e.
forging the response packets so that they appear to come from your server) then the only way to tell would be to place a deliberately wrong IP entry for a well known address on your server (i.e.
something that Comcast wouldn't know about) and then run the query again to see if you get the wrong result (no redirection or impersonation) OR if you get the expected result (redirection or impersonation).
Also, they might only be forwarding queries that they don't recognize to your server so that any custom or unusual queries hit your server but stuff like google.com is answered by their server(s).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271291</id>
	<title>what is a port?</title>
	<author>Anonymous</author>
	<datestamp>1244540580000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>ok, I already know it is like a train station but for ships. However, I am still looking online describing what is a port (i.e. Port 53, Port 80, 88, etc.).</p></htmltext>
<tokenext>ok , I already know it is like a train station but for ships .
However , I am still looking online describing what is a port ( i.e .
Port 53 , Port 80 , 88 , etc .
) .</tokentext>
<sentencetext>ok, I already know it is like a train station but for ships.
However, I am still looking online describing what is a port (i.e.
Port 53, Port 80, 88, etc.
).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269893</id>
	<title>Re:Is this happening for ANYONE?</title>
	<author>Anonymous</author>
	<datestamp>1244577960000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>OMG!!! Toyota sucks no one should buy one or they are Communist!</p></htmltext>
<tokenext>OMG ! ! !
Toyota sucks no one should buy one or they are Communist !</tokentext>
<sentencetext>OMG!!!
Toyota sucks no one should buy one or they are Communist!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269435</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270221</id>
	<title>Re:The scary part</title>
	<author>Culture20</author>
	<datestamp>1244579160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>In other words, it gives ICANN even stronger dominance over internet naming.</p></div><p>Technically, it gives local ISPs stronger dominance over internet naming.  Not that they can enforce it beyond their fiefdom...</p></div>
	</htmltext>
<tokenext>In other words , it gives ICANN even stronger dominance over internet naming.Technically , it gives local ISPs stronger dominance over internet naming .
Not that they can enforce it beyond their fiefdom.. .</tokentext>
<sentencetext>In other words, it gives ICANN even stronger dominance over internet naming.Technically, it gives local ISPs stronger dominance over internet naming.
Not that they can enforce it beyond their fiefdom...
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269295</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269275</id>
	<title>Re:Fuck `Em All</title>
	<author>Anonymous</author>
	<datestamp>1244575620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><i>Yes, because hijacking your DNS packets and injecting RST packets to interfere with bittorrent is comparable to putting millions of people in ovens and trying to conquer Eurasia......</i> <br> <br>

Good point, although I think the result will be the same for both: failure.</htmltext>
<tokenext>Yes , because hijacking your DNS packets and injecting RST packets to interfere with bittorrent is comparable to putting millions of people in ovens and trying to conquer Eurasia..... . Good point , although I think the result will be the same for both : failure .</tokentext>
<sentencetext>Yes, because hijacking your DNS packets and injecting RST packets to interfere with bittorrent is comparable to putting millions of people in ovens and trying to conquer Eurasia......  

Good point, although I think the result will be the same for both: failure.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269171</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270179</id>
	<title>"Official Response"</title>
	<author>Anonymous</author>
	<datestamp>1244579100000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext>Wow it's nice to know that Comcast has both a twitter account and a brand new Slashdot account.  Oh, it's most likely that you're an employee (maybe tech support), I'd watch what you call an 'Official Response' as many corporations have very strict rules about talking to the press, or making any binding claims to a general audience.   Are you authorized for such communication?  If so, I'd suggest a listing on the main corporate 'contacts' page, so that it'd be easy to verify it as 'official'. Also, the DNS team (or even the guy on duty) might not be complicit in the skulduggery, so your assessment might not be correct.</htmltext>
<tokenext>Wow it 's nice to know that Comcast has both a twitter account and a brand new Slashdot account .
Oh , it 's most likely that you 're an employee ( maybe tech support ) , I 'd watch what you call an 'Official Response ' as many corporations have very strict rules about talking to the press , or making any binding claims to a general audience .
Are you authorized for such communication ?
If so , I 'd suggest a listing on the main corporate 'contacts ' page , so that it 'd be easy to verify it as 'official' .
Also , the DNS team ( or even the guy on duty ) might not be complicit in the skulduggery , so your assessment might not be correct .</tokentext>
<sentencetext>Wow it's nice to know that Comcast has both a twitter account and a brand new Slashdot account.
Oh, it's most likely that you're an employee (maybe tech support), I'd watch what you call an 'Official Response' as many corporations have very strict rules about talking to the press, or making any binding claims to a general audience.
Are you authorized for such communication?
If so, I'd suggest a listing on the main corporate 'contacts' page, so that it'd be easy to verify it as 'official'.
Also, the DNS team (or even the guy on duty) might not be complicit in the skulduggery, so your assessment might not be correct.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269531</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270063</id>
	<title>Netalyzr indicates not filtered in OR</title>
	<author>The Master Control P</author>
	<datestamp>1244578680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Direct UDP access to remote DNS servers (port 53) is allowed.
The applet was also able to directly request a large DNS response.</p></div></blockquote><p>

I, for one, am absolutely astounded that<nobr> <wbr></nobr>/.'s editors would post some blog rant without fact checking it first... That would be irresponsible to the point of incompetent, something virtually unheard of around here.<br> <br>

It's not as if <i>the original blog ranter</i> said "Full disclosure: I dont know if its Comcast or Earthlink thats responsible for this behavior..." or anything. Screw it, he's not getting in the way of your Two Minute's Hate!</p></div>
	</htmltext>
<tokenext>Direct UDP access to remote DNS servers ( port 53 ) is allowed .
The applet was also able to directly request a large DNS response .
I , for one , am absolutely astounded that / .
's editors would post some blog rant without fact checking it first... That would be irresponsible to the point of incompetent , something virtually unheard of around here .
It 's not as if the original blog ranter said " Full disclosure : I dont know if its Comcast or Earthlink thats responsible for this behavior... " or anything .
Screw it , he 's not getting in the way of your Two Minute 's Hate !</tokentext>
<sentencetext>Direct UDP access to remote DNS servers (port 53) is allowed.
The applet was also able to directly request a large DNS response.
I, for one, am absolutely astounded that /.
's editors would post some blog rant without fact checking it first... That would be irresponsible to the point of incompetent, something virtually unheard of around here.
It's not as if the original blog ranter said "Full disclosure: I dont know if its Comcast or Earthlink thats responsible for this behavior..." or anything.
Screw it, he's not getting in the way of your Two Minute's Hate!
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270699</id>
	<title>Re:Damn! That may stop my plan......</title>
	<author>Anonymous</author>
	<datestamp>1244581080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Which is why you should be using port 443 for your openvpn server. No one's going to block https.</p></htmltext>
<tokenext>Which is why you should be using port 443 for your openvpn server .
No one 's going to block https .</tokentext>
<sentencetext>Which is why you should be using port 443 for your openvpn server.
No one's going to block https.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269365</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271505</id>
	<title>Not on OpenDNS</title>
	<author>pvera</author>
	<datestamp>1244541420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>At least for Comcast in zip 20190:</p><p>$ nslookup<br>&gt; insomniaccoder.com<br>Server:         208.67.222.222<br>Address:        208.67.222.222#53</p><p>Non-authoritative answer:<br>Name:   insomniaccoder.com<br>Address: 72.32.231.8</p><p>That's one of the two OpenDNS servers on port 53. Unless Comcast is faking/proxying/whatever the traffic and responding with OpenDNS' IP address.</p></htmltext>
<tokenext>At least for Comcast in zip 20190 : $ nslookup &gt; insomniaccoder.comServer : 208.67.222.222Address : 208.67.222.222 # 53Non-authoritative answer : Name : insomniaccoder.comAddress : 72.32.231.8That 's one of the two OpenDNS servers on port 53 .
Unless Comcast is faking/proxying/whatever the traffic and responding with OpenDNS ' IP address .</tokentext>
<sentencetext>At least for Comcast in zip 20190:$ nslookup&gt; insomniaccoder.comServer:         208.67.222.222Address:        208.67.222.222#53Non-authoritative answer:Name:   insomniaccoder.comAddress: 72.32.231.8That's one of the two OpenDNS servers on port 53.
Unless Comcast is faking/proxying/whatever the traffic and responding with OpenDNS' IP address.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269365</id>
	<title>Damn! That may stop my plan......</title>
	<author>whoever57</author>
	<datestamp>1244575860000</datestamp>
	<modclass>Funny</modclass>
	<modscore>3</modscore>
	<htmltext>Last time I had some spare time in an airport, I found that the T-Mobile hotspot allowed 53/UDP traffic out, so I was thinking of setting up openvpn on port 53 (instead of its usual 1194) in order to access my home machines (without a T-Mobile login). If Comcast intercepts this traffic, my evil plan won't work!</htmltext>
<tokenext>Last time I had some spare time in an airport , I found that the T-Mobile hotspot allowed 53/UDP traffic out , so I was thinking of setting up openvpn on port 53 ( instead of its usual 1194 ) in order to access my home machines ( without a T-Mobile login ) .
If Comcast intercepts this traffic , my evil plan wo n't work !</tokentext>
<sentencetext>Last time I had some spare time in an airport, I found that the T-Mobile hotspot allowed 53/UDP traffic out, so I was thinking of setting up openvpn on port 53 (instead of its usual 1194) in order to access my home machines (without a T-Mobile login).
If Comcast intercepts this traffic, my evil plan won't work!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269351</id>
	<title>Re:Fuck `Em All</title>
	<author>Trivial\_Zeros</author>
	<datestamp>1244575860000</datestamp>
	<modclass>Funny</modclass>
	<modscore>2</modscore>
	<htmltext>It's not evil... It's Comcastic!</htmltext>
<tokenext>It 's not evil... It 's Comcastic !</tokentext>
<sentencetext>It's not evil... It's Comcastic!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269621</id>
	<title>Re:Not happening to me</title>
	<author>mea37</author>
	<datestamp>1244576700000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>That's the <i>only</i> way you can think of to verify what's happening?</p><p>GP controls the DNS server in question.  Think server logs and monitoring tools.</p></htmltext>
<tokenext>That 's the only way you can think of to verify what 's happening ? GP controls the DNS server in question .
Think server logs and monitoring tools .</tokentext>
<sentencetext>That's the only way you can think of to verify what's happening?GP controls the DNS server in question.
Think server logs and monitoring tools.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269251</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271459</id>
	<title>mysterious international terr org, works in US ?</title>
	<author>x4r</author>
	<datestamp>1244541300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>I'm a comcast user and it works for me...perhaps his home network is the problem.  A Linux user having a misconfigured network?!??!  Oh wait this is Slashdot...nevermind.</p></div><p>because interfering-exploiting DNS(can't wait 4 imes, where DNSSec infrastructure are become mandator ISP license aquiring(&amp;Native IPv6 perhaps !))
easiest way to build botnets and/or use ISp 4 inteligency gathering.
i mean, this case must be investigated by NSA, not FTC.</p></div>
	</htmltext>
<tokenext>I 'm a comcast user and it works for me...perhaps his home network is the problem .
A Linux user having a misconfigured network ? ! ? ? !
Oh wait this is Slashdot...nevermind.because interfering-exploiting DNS ( ca n't wait 4 imes , where DNSSec infrastructure are become mandator ISP license aquiring ( &amp;Native IPv6 perhaps !
) ) easiest way to build botnets and/or use ISp 4 inteligency gathering .
i mean , this case must be investigated by NSA , not FTC .</tokentext>
<sentencetext>I'm a comcast user and it works for me...perhaps his home network is the problem.
A Linux user having a misconfigured network?!??!
Oh wait this is Slashdot...nevermind.because interfering-exploiting DNS(can't wait 4 imes, where DNSSec infrastructure are become mandator ISP license aquiring(&amp;Native IPv6 perhaps !
))
easiest way to build botnets and/or use ISp 4 inteligency gathering.
i mean, this case must be investigated by NSA, not FTC.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269659</id>
	<title>Have to test tonight.</title>
	<author>Rene S. Hollan</author>
	<datestamp>1244576940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I have the luxury of residential AND commercial internet service from Comcast in Monroe, WA. I can try both tonight.</p></htmltext>
<tokenext>I have the luxury of residential AND commercial internet service from Comcast in Monroe , WA .
I can try both tonight .</tokentext>
<sentencetext>I have the luxury of residential AND commercial internet service from Comcast in Monroe, WA.
I can try both tonight.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273953</id>
	<title>What is the real motive here ??  to access netalyz</title>
	<author>Anonymous</author>
	<datestamp>1244557080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Well, there may be another motive to this original post than has been discussed here.</p><p>And it's sinister too.</p><p>In order to run the suggested test which the OP requests, one must allow the "Netalyzer" JS access to your machine.  And that is an excellent way to investigate and acquire "interesting" data on people.  Does this ring any bells??</p><p>So now Netaylzer people will have an interesting list of Slash-dotters who are concerned about this &amp; Comcast issues in general.  Ah at least then we will be safer than before we had that list of subversive "Slash-dotters".</p><p>Wonder where htey will use this newly acquired information. ????</p></htmltext>
<tokenext>Well , there may be another motive to this original post than has been discussed here.And it 's sinister too.In order to run the suggested test which the OP requests , one must allow the " Netalyzer " JS access to your machine .
And that is an excellent way to investigate and acquire " interesting " data on people .
Does this ring any bells ?
? So now Netaylzer people will have an interesting list of Slash-dotters who are concerned about this &amp; Comcast issues in general .
Ah at least then we will be safer than before we had that list of subversive " Slash-dotters " .Wonder where htey will use this newly acquired information .
? ? ? ?</tokentext>
<sentencetext>Well, there may be another motive to this original post than has been discussed here.And it's sinister too.In order to run the suggested test which the OP requests, one must allow the "Netalyzer" JS access to your machine.
And that is an excellent way to investigate and acquire "interesting" data on people.
Does this ring any bells?
?So now Netaylzer people will have an interesting list of Slash-dotters who are concerned about this &amp; Comcast issues in general.
Ah at least then we will be safer than before we had that list of subversive "Slash-dotters".Wonder where htey will use this newly acquired information.
????</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270559</id>
	<title>Re:Netalyzer results</title>
	<author>Anonymous</author>
	<datestamp>1244580420000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p> <a href="http://netalyzr.icsi.berkeley.edu/restore/id=ae8199f5-18807-f5eeee66-ce59-42a4-8803" title="berkeley.edu" rel="nofollow">http://netalyzr.icsi.berkeley.edu/restore/id=ae8199f5-18807-f5eeee66-ce59-42a4-8803</a> [berkeley.edu] </p><p>Note that my DNS servers are Level3 servers (4.2.2.2, 4.2.2.4) since they are much faster than Comcast DNS.</p></div><p>Not only are they faster, but IME comcast's servers go down on a fucking weekly basis. Totally unacceptable.</p><p>Additionally, as comcast is a level 3 customer, they're not going to be blocking us from using those any time soon.</p></div>
	</htmltext>
<tokenext>http : //netalyzr.icsi.berkeley.edu/restore/id = ae8199f5-18807-f5eeee66-ce59-42a4-8803 [ berkeley.edu ] Note that my DNS servers are Level3 servers ( 4.2.2.2 , 4.2.2.4 ) since they are much faster than Comcast DNS.Not only are they faster , but IME comcast 's servers go down on a fucking weekly basis .
Totally unacceptable.Additionally , as comcast is a level 3 customer , they 're not going to be blocking us from using those any time soon .</tokentext>
<sentencetext> http://netalyzr.icsi.berkeley.edu/restore/id=ae8199f5-18807-f5eeee66-ce59-42a4-8803 [berkeley.edu] Note that my DNS servers are Level3 servers (4.2.2.2, 4.2.2.4) since they are much faster than Comcast DNS.Not only are they faster, but IME comcast's servers go down on a fucking weekly basis.
Totally unacceptable.Additionally, as comcast is a level 3 customer, they're not going to be blocking us from using those any time soon.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269323</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272755</id>
	<title>No DNS issues here...</title>
	<author>Anonymous</author>
	<datestamp>1244548320000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>http://netalyzr.icsi.berkeley.edu/restore/id=4b65af4b-21402-5204573b-cf62-4504-84c7 permalink from the ICSI Netalyzr from a comcast user in Utah.  Doesn't show any DNS issues.<br>I do however, know that comcast is fail, and unreliable as shit.</p></htmltext>
<tokenext>http : //netalyzr.icsi.berkeley.edu/restore/id = 4b65af4b-21402-5204573b-cf62-4504-84c7 permalink from the ICSI Netalyzr from a comcast user in Utah .
Does n't show any DNS issues.I do however , know that comcast is fail , and unreliable as shit .</tokentext>
<sentencetext>http://netalyzr.icsi.berkeley.edu/restore/id=4b65af4b-21402-5204573b-cf62-4504-84c7 permalink from the ICSI Netalyzr from a comcast user in Utah.
Doesn't show any DNS issues.I do however, know that comcast is fail, and unreliable as shit.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269077</id>
	<title>DNSSEC?</title>
	<author>Anonymous</author>
	<datestamp>1244575020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>How does this affect DNS with DNSSEC applied? Wouldn't there be a mismatch in the signing keys?</htmltext>
<tokenext>How does this affect DNS with DNSSEC applied ?
Would n't there be a mismatch in the signing keys ?</tokentext>
<sentencetext>How does this affect DNS with DNSSEC applied?
Wouldn't there be a mismatch in the signing keys?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271549</id>
	<title>Re:Fuck `Em All</title>
	<author>Anonymous</author>
	<datestamp>1244541660000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>have you ever *seen* a RST packet???</p></htmltext>
<tokenext>have you ever * seen * a RST packet ? ?
?</tokentext>
<sentencetext>have you ever *seen* a RST packet??
?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269171</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270455</id>
	<title>Re:Port 53 Rerouted in Seattle :|</title>
	<author>DarthVain</author>
	<datestamp>1244580120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Sounds a lot like this:</p><p><a href="http://www.gucomics.com/comic/?cdate=20090527" title="gucomics.com">http://www.gucomics.com/comic/?cdate=20090527</a> [gucomics.com]</p></htmltext>
<tokenext>Sounds a lot like this : http : //www.gucomics.com/comic/ ? cdate = 20090527 [ gucomics.com ]</tokentext>
<sentencetext>Sounds a lot like this:http://www.gucomics.com/comic/?cdate=20090527 [gucomics.com]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269633</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275281</id>
	<title>Appears to be blocking in my area..</title>
	<author>Anonymous</author>
	<datestamp>1244569020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I'm a comcast customer from Indiana with a "sticky" ip, though not a true static.  It appears that they're messing with the DNS in my area</p><p>http://tinyurl.com/ncghzc</p></htmltext>
<tokenext>I 'm a comcast customer from Indiana with a " sticky " ip , though not a true static .
It appears that they 're messing with the DNS in my areahttp : //tinyurl.com/ncghzc</tokentext>
<sentencetext>I'm a comcast customer from Indiana with a "sticky" ip, though not a true static.
It appears that they're messing with the DNS in my areahttp://tinyurl.com/ncghzc</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28276543</id>
	<title>FTFS:</title>
	<author>Anonymous</author>
	<datestamp>1244624460000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>"If true, this is a pretty serious escalation in the Net Neutrality wars."</p><p>Now, you can either wait until Comcast say they do, or don't. You can wait until someone else says it's happening too. Or you can post it and let people say on the blog that they don't see it.</p><p>Now that last one won't happen UNLESS someone reports widely enough this accusation. Without wide reporting, if it's a local problem, it will get blown out of proportion since only local people will hear of it and check.</p><p>If it doesn't get widely reported, it won't be tested and it could stay unresolved. Then 2 years down the line someone will hear of this and say "In the past, Comcast has...". There's no proof it didn't happen, is there.</p><p>So slashdot HAS done the right thing.</p></htmltext>
<tokenext>" If true , this is a pretty serious escalation in the Net Neutrality wars .
" Now , you can either wait until Comcast say they do , or do n't .
You can wait until someone else says it 's happening too .
Or you can post it and let people say on the blog that they do n't see it.Now that last one wo n't happen UNLESS someone reports widely enough this accusation .
Without wide reporting , if it 's a local problem , it will get blown out of proportion since only local people will hear of it and check.If it does n't get widely reported , it wo n't be tested and it could stay unresolved .
Then 2 years down the line someone will hear of this and say " In the past , Comcast has... " .
There 's no proof it did n't happen , is there.So slashdot HAS done the right thing .</tokentext>
<sentencetext>"If true, this is a pretty serious escalation in the Net Neutrality wars.
"Now, you can either wait until Comcast say they do, or don't.
You can wait until someone else says it's happening too.
Or you can post it and let people say on the blog that they don't see it.Now that last one won't happen UNLESS someone reports widely enough this accusation.
Without wide reporting, if it's a local problem, it will get blown out of proportion since only local people will hear of it and check.If it doesn't get widely reported, it won't be tested and it could stay unresolved.
Then 2 years down the line someone will hear of this and say "In the past, Comcast has...".
There's no proof it didn't happen, is there.So slashdot HAS done the right thing.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269573</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269475</id>
	<title>California?</title>
	<author>Anonymous</author>
	<datestamp>1244576220000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>0</modscore>
	<htmltext><p>Californians are in some kind of budget crisis...or are they? I am in Timbuktu if that matters.</p></htmltext>
<tokenext>Californians are in some kind of budget crisis...or are they ?
I am in Timbuktu if that matters .</tokentext>
<sentencetext>Californians are in some kind of budget crisis...or are they?
I am in Timbuktu if that matters.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270441</id>
	<title>Re:Port 53 Rerouted in Seattle :|</title>
	<author>clone53421</author>
	<datestamp>1244580060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Um, those Webalyzer results show that port 53 was connecting just fine.</p></htmltext>
<tokenext>Um , those Webalyzer results show that port 53 was connecting just fine .</tokentext>
<sentencetext>Um, those Webalyzer results show that port 53 was connecting just fine.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269633</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273545</id>
	<title>No Problems, and some more info...</title>
	<author>archiac</author>
	<datestamp>1244553780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><a href="http://n18.netalyzr.icsi.berkeley.edu/summary/id=ae817952-25497-39a13fe0-7769-4072-beae" title="berkeley.edu" rel="nofollow">http://n18.netalyzr.icsi.berkeley.edu/summary/id=ae817952-25497-39a13fe0-7769-4072-beae</a> [berkeley.edu]

All seems fine to me.
So if you really want to test this..
Change your resolver to 70.88.178.97 (Comcast Business IP) and then attempt to lookup some name such as <a href="http://atlantic.ocean/" title="atlantic.ocean" rel="nofollow">http://atlantic.ocean/</a> [atlantic.ocean] or <a href="http://www.servers.ucann2/" title="www.servers.ucann2" rel="nofollow">http://www.servers.ucann2/</a> [www.servers.ucann2]

The second page is a parked page which is correct, the first page should give you a ftp style listing, if you do not get either of these pages, then you may be experiencing this type of hijacking. But I highly doubt this would be performed on commercial accounts, maybe residential.

David - UCANN2</htmltext>
<tokenext>http : //n18.netalyzr.icsi.berkeley.edu/summary/id = ae817952-25497-39a13fe0-7769-4072-beae [ berkeley.edu ] All seems fine to me .
So if you really want to test this. . Change your resolver to 70.88.178.97 ( Comcast Business IP ) and then attempt to lookup some name such as http : //atlantic.ocean/ [ atlantic.ocean ] or http : //www.servers.ucann2/ [ www.servers.ucann2 ] The second page is a parked page which is correct , the first page should give you a ftp style listing , if you do not get either of these pages , then you may be experiencing this type of hijacking .
But I highly doubt this would be performed on commercial accounts , maybe residential .
David - UCANN2</tokentext>
<sentencetext>http://n18.netalyzr.icsi.berkeley.edu/summary/id=ae817952-25497-39a13fe0-7769-4072-beae [berkeley.edu]

All seems fine to me.
So if you really want to test this..
Change your resolver to 70.88.178.97 (Comcast Business IP) and then attempt to lookup some name such as http://atlantic.ocean/ [atlantic.ocean] or http://www.servers.ucann2/ [www.servers.ucann2]

The second page is a parked page which is correct, the first page should give you a ftp style listing, if you do not get either of these pages, then you may be experiencing this type of hijacking.
But I highly doubt this would be performed on commercial accounts, maybe residential.
David - UCANN2</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269141</id>
	<title>No problems for me</title>
	<author>Anonymous</author>
	<datestamp>1244575200000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I use opendns and it seems to be functioning fine.  My requests show up on my account and I get the occasional Opendns search if I misstype something.</p></htmltext>
<tokenext>I use opendns and it seems to be functioning fine .
My requests show up on my account and I get the occasional Opendns search if I misstype something .</tokentext>
<sentencetext>I use opendns and it seems to be functioning fine.
My requests show up on my account and I get the occasional Opendns search if I misstype something.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271229</id>
	<title>Re:Not happening to me</title>
	<author>Cyner</author>
	<datestamp>1244540220000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I've got a consumer account and run a similar setup. My IP has changed 3 times in 7 years. Having to deal with the change once every few years isn't much for the cost savings; especially when it's just my domain.</p></htmltext>
<tokenext>I 've got a consumer account and run a similar setup .
My IP has changed 3 times in 7 years .
Having to deal with the change once every few years is n't much for the cost savings ; especially when it 's just my domain .</tokentext>
<sentencetext>I've got a consumer account and run a similar setup.
My IP has changed 3 times in 7 years.
Having to deal with the change once every few years isn't much for the cost savings; especially when it's just my domain.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269131</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28280813</id>
	<title>Re:Not happening to me</title>
	<author>Anonymous</author>
	<datestamp>1244653680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I get exactly the same result, but I'm on a T1 and have nothing to do with Comcast.</p></htmltext>
<tokenext>I get exactly the same result , but I 'm on a T1 and have nothing to do with Comcast .</tokentext>
<sentencetext>I get exactly the same result, but I'm on a T1 and have nothing to do with Comcast.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269637</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017</id>
	<title>Not happening to me</title>
	<author>jimmyhat3939</author>
	<datestamp>1244574780000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><p>I'm a Comcast user, and I run a DNS server for a few private domains that only I use. I have not experienced this, and I just verified that it's not currently happening. I'm in California if that matters.</p></htmltext>
<tokenext>I 'm a Comcast user , and I run a DNS server for a few private domains that only I use .
I have not experienced this , and I just verified that it 's not currently happening .
I 'm in California if that matters .</tokentext>
<sentencetext>I'm a Comcast user, and I run a DNS server for a few private domains that only I use.
I have not experienced this, and I just verified that it's not currently happening.
I'm in California if that matters.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273813</id>
	<title>Maryland reporting in</title>
	<author>stevegee58</author>
	<datestamp>1244556060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><a href="http://netalyzr.icsi.berkeley.edu/restore/id=ae819c33-24534-54c0c922-5d71-4950-9aea" title="berkeley.edu" rel="nofollow">http://netalyzr.icsi.berkeley.edu/restore/id=ae819c33-24534-54c0c922-5d71-4950-9aea</a> [berkeley.edu]</htmltext>
<tokenext>http : //netalyzr.icsi.berkeley.edu/restore/id = ae819c33-24534-54c0c922-5d71-4950-9aea [ berkeley.edu ]</tokentext>
<sentencetext>http://netalyzr.icsi.berkeley.edu/restore/id=ae819c33-24534-54c0c922-5d71-4950-9aea [berkeley.edu]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269097</id>
	<title>Re:Not happening to me</title>
	<author>kenp2002</author>
	<datestamp>1244575080000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext><p>screen shot or it didn't happen<nobr> <wbr></nobr>;)</p></htmltext>
<tokenext>screen shot or it did n't happen ; )</tokentext>
<sentencetext>screen shot or it didn't happen ;)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275167</id>
	<title>Cavalier Dsl Delaware</title>
	<author>Anonymous</author>
	<datestamp>1244568300000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Noteworthy Events<br>Major Abnormalities</p><p>We received unexpected and possibly dangerous results when looking up important names<br>Your DNS resolver returns results even when no such server exists</p><p>Minor Aberrations</p><p>Your computer's clock is slightly fast</p><p>Address-based Tests<br>NAT detection: No NAT Detected</p><p>Your global IP address is 98.141.97.123 and matches your local one. You are not behind a NAT.</p><p>Your machine numbers TCP source ports sequentially. The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis.</p><p>DNS-based host information: OK</p><p>You are not a Tor exit node for HTTP traffic. You are not listed on any Spamhaus blacklists. The SORBS DUHL believes you are using a statically assigned IP address.<br>Reachability Tests<br>General connectivity: OK</p><p>Basic UDP access is available. Direct UDP access to remote DNS servers (port 53) is allowed.<br>The applet was also able to directly request a large DNS response. Direct UDP access to remote MSSQL servers (port 1434) is allowed. Direct TCP access to remote FTP servers (port 21) is allowed. Direct TCP access to remote SSH servers (port 22) is allowed. Direct TCP access to remote SMTP servers (port 25) is allowed. Direct TCP access to remote DNS servers (port 53) is allowed. Direct TCP access to remote HTTP servers (port 80) is allowed. Direct TCP access to remote POP servers (port 110) is allowed. Direct TCP access to remote RPC servers (port 135) is allowed. Direct TCP access to remote NetBIOS servers (port 139) is blocked.<br>This is probably for security reasons, as this protocol is generally not designed for use outside the local network. Direct TCP access to remote IMAP servers (port 143) is allowed. Direct TCP access to remote SNMP servers (port 161) is allowed. Direct TCP access to remote HTTPS servers (port 443) is allowed. Direct TCP access to remote SMB servers (port 445) is allowed. Direct TCP access to remote SMTP/SSL servers (port 465) is allowed. Direct TCP access to remote secure IMAP servers (port 585) is allowed. Direct TCP access to remote authenticated SMTP servers (port 587) is allowed. Direct TCP access to remote IMAP/SSL servers (port 993) is allowed. Direct TCP access to remote POP/SSL servers (port 995) is allowed. Direct TCP access to remote SIP servers (port 5060) is allowed. Direct TCP access to remote BitTorrent servers (port 6881) is allowed.<br>Network Access Link Properties<br>Network latency measurements: Latency: 46ms Loss: 0.0\%</p><p>The round-trip time (RTT) between your computer and our server is 46 msec, which is good. We recorded no packet loss between your system and our server.<br>TCP connection setup latency: 48ms</p><p>The time it takes your computer to set up a TCP connection with our server is 48 msec, which is good.<br>Network bandwidth measurements: Upload 920 Kbit/sec, Download 4.7 Mbit/sec</p><p>Your Uplink: We measured your uplink's sending bandwidth at 920 Kbit/sec. This level of bandwidth works well for many users. Your Downlink: We measured your downlink's receiving bandwidth at 4.7 Mbit/sec. This level of bandwidth works well for many users.<br>Network buffer measurements: Uplink 300 ms, Downlink 69 ms</p><p>We estimate your uplink as having 300 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic. We estimate your downlink as having 69 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.<br>HTTP Tests<br>Address-based HTTP proxy detection: OK</p><p>There is no explicit sign of HTTP proxy use based on IP address.<br>Header-based HTTP proxy detection: OK</p><p>No HTTP header or content changes hint at the presence of a proxy.<br>HTTP proxy detection via malformed requests: OK</p><p>Deliberately malformed HTTP requests arrive at our server unchanged. We are not able to detect a proxy along the path to our server using this method.<br>Filetype-based filtering: OK</p></htmltext>
<tokenext>Noteworthy EventsMajor AbnormalitiesWe received unexpected and possibly dangerous results when looking up important namesYour DNS resolver returns results even when no such server existsMinor AberrationsYour computer 's clock is slightly fastAddress-based TestsNAT detection : No NAT DetectedYour global IP address is 98.141.97.123 and matches your local one .
You are not behind a NAT.Your machine numbers TCP source ports sequentially .
The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis.DNS-based host information : OKYou are not a Tor exit node for HTTP traffic .
You are not listed on any Spamhaus blacklists .
The SORBS DUHL believes you are using a statically assigned IP address.Reachability TestsGeneral connectivity : OKBasic UDP access is available .
Direct UDP access to remote DNS servers ( port 53 ) is allowed.The applet was also able to directly request a large DNS response .
Direct UDP access to remote MSSQL servers ( port 1434 ) is allowed .
Direct TCP access to remote FTP servers ( port 21 ) is allowed .
Direct TCP access to remote SSH servers ( port 22 ) is allowed .
Direct TCP access to remote SMTP servers ( port 25 ) is allowed .
Direct TCP access to remote DNS servers ( port 53 ) is allowed .
Direct TCP access to remote HTTP servers ( port 80 ) is allowed .
Direct TCP access to remote POP servers ( port 110 ) is allowed .
Direct TCP access to remote RPC servers ( port 135 ) is allowed .
Direct TCP access to remote NetBIOS servers ( port 139 ) is blocked.This is probably for security reasons , as this protocol is generally not designed for use outside the local network .
Direct TCP access to remote IMAP servers ( port 143 ) is allowed .
Direct TCP access to remote SNMP servers ( port 161 ) is allowed .
Direct TCP access to remote HTTPS servers ( port 443 ) is allowed .
Direct TCP access to remote SMB servers ( port 445 ) is allowed .
Direct TCP access to remote SMTP/SSL servers ( port 465 ) is allowed .
Direct TCP access to remote secure IMAP servers ( port 585 ) is allowed .
Direct TCP access to remote authenticated SMTP servers ( port 587 ) is allowed .
Direct TCP access to remote IMAP/SSL servers ( port 993 ) is allowed .
Direct TCP access to remote POP/SSL servers ( port 995 ) is allowed .
Direct TCP access to remote SIP servers ( port 5060 ) is allowed .
Direct TCP access to remote BitTorrent servers ( port 6881 ) is allowed.Network Access Link PropertiesNetwork latency measurements : Latency : 46ms Loss : 0.0 \ % The round-trip time ( RTT ) between your computer and our server is 46 msec , which is good .
We recorded no packet loss between your system and our server.TCP connection setup latency : 48msThe time it takes your computer to set up a TCP connection with our server is 48 msec , which is good.Network bandwidth measurements : Upload 920 Kbit/sec , Download 4.7 Mbit/secYour Uplink : We measured your uplink 's sending bandwidth at 920 Kbit/sec .
This level of bandwidth works well for many users .
Your Downlink : We measured your downlink 's receiving bandwidth at 4.7 Mbit/sec .
This level of bandwidth works well for many users.Network buffer measurements : Uplink 300 ms , Downlink 69 msWe estimate your uplink as having 300 msec of buffering .
This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic .
We estimate your downlink as having 69 msec of buffering .
This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.HTTP TestsAddress-based HTTP proxy detection : OKThere is no explicit sign of HTTP proxy use based on IP address.Header-based HTTP proxy detection : OKNo HTTP header or content changes hint at the presence of a proxy.HTTP proxy detection via malformed requests : OKDeliberately malformed HTTP requests arrive at our server unchanged .
We are not able to detect a proxy along the path to our server using this method.Filetype-based filtering : OK</tokentext>
<sentencetext>Noteworthy EventsMajor AbnormalitiesWe received unexpected and possibly dangerous results when looking up important namesYour DNS resolver returns results even when no such server existsMinor AberrationsYour computer's clock is slightly fastAddress-based TestsNAT detection: No NAT DetectedYour global IP address is 98.141.97.123 and matches your local one.
You are not behind a NAT.Your machine numbers TCP source ports sequentially.
The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis.DNS-based host information: OKYou are not a Tor exit node for HTTP traffic.
You are not listed on any Spamhaus blacklists.
The SORBS DUHL believes you are using a statically assigned IP address.Reachability TestsGeneral connectivity: OKBasic UDP access is available.
Direct UDP access to remote DNS servers (port 53) is allowed.The applet was also able to directly request a large DNS response.
Direct UDP access to remote MSSQL servers (port 1434) is allowed.
Direct TCP access to remote FTP servers (port 21) is allowed.
Direct TCP access to remote SSH servers (port 22) is allowed.
Direct TCP access to remote SMTP servers (port 25) is allowed.
Direct TCP access to remote DNS servers (port 53) is allowed.
Direct TCP access to remote HTTP servers (port 80) is allowed.
Direct TCP access to remote POP servers (port 110) is allowed.
Direct TCP access to remote RPC servers (port 135) is allowed.
Direct TCP access to remote NetBIOS servers (port 139) is blocked.This is probably for security reasons, as this protocol is generally not designed for use outside the local network.
Direct TCP access to remote IMAP servers (port 143) is allowed.
Direct TCP access to remote SNMP servers (port 161) is allowed.
Direct TCP access to remote HTTPS servers (port 443) is allowed.
Direct TCP access to remote SMB servers (port 445) is allowed.
Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.
Direct TCP access to remote secure IMAP servers (port 585) is allowed.
Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.
Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.
Direct TCP access to remote POP/SSL servers (port 995) is allowed.
Direct TCP access to remote SIP servers (port 5060) is allowed.
Direct TCP access to remote BitTorrent servers (port 6881) is allowed.Network Access Link PropertiesNetwork latency measurements: Latency: 46ms Loss: 0.0\%The round-trip time (RTT) between your computer and our server is 46 msec, which is good.
We recorded no packet loss between your system and our server.TCP connection setup latency: 48msThe time it takes your computer to set up a TCP connection with our server is 48 msec, which is good.Network bandwidth measurements: Upload 920 Kbit/sec, Download 4.7 Mbit/secYour Uplink: We measured your uplink's sending bandwidth at 920 Kbit/sec.
This level of bandwidth works well for many users.
Your Downlink: We measured your downlink's receiving bandwidth at 4.7 Mbit/sec.
This level of bandwidth works well for many users.Network buffer measurements: Uplink 300 ms, Downlink 69 msWe estimate your uplink as having 300 msec of buffering.
This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.
We estimate your downlink as having 69 msec of buffering.
This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.HTTP TestsAddress-based HTTP proxy detection: OKThere is no explicit sign of HTTP proxy use based on IP address.Header-based HTTP proxy detection: OKNo HTTP header or content changes hint at the presence of a proxy.HTTP proxy detection via malformed requests: OKDeliberately malformed HTTP requests arrive at our server unchanged.
We are not able to detect a proxy along the path to our server using this method.Filetype-based filtering: OK</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269323</id>
	<title>Netalyzer results</title>
	<author>MostAwesomeDude</author>
	<datestamp>1244575800000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p><a href="http://netalyzr.icsi.berkeley.edu/restore/id=ae8199f5-18807-f5eeee66-ce59-42a4-8803" title="berkeley.edu">http://netalyzr.icsi.berkeley.edu/restore/id=ae8199f5-18807-f5eeee66-ce59-42a4-8803</a> [berkeley.edu]</p><p>Note that my DNS servers are Level3 servers (4.2.2.2, 4.2.2.4) since they are much faster than Comcast DNS.</p></htmltext>
<tokenext>http : //netalyzr.icsi.berkeley.edu/restore/id = ae8199f5-18807-f5eeee66-ce59-42a4-8803 [ berkeley.edu ] Note that my DNS servers are Level3 servers ( 4.2.2.2 , 4.2.2.4 ) since they are much faster than Comcast DNS .</tokentext>
<sentencetext>http://netalyzr.icsi.berkeley.edu/restore/id=ae8199f5-18807-f5eeee66-ce59-42a4-8803 [berkeley.edu]Note that my DNS servers are Level3 servers (4.2.2.2, 4.2.2.4) since they are much faster than Comcast DNS.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269885</id>
	<title>Re:Not happening to me</title>
	<author>johannesg</author>
	<datestamp>1244577900000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><blockquote><div><p>I just verified that it's not currently happening. I'm in California if that matters.</p></div></blockquote><p>Me too. I'm also in CA and it is not curently happening.</p></div><p>Are you saying this is currently <a href="http://www.youtube.com/watch?v=zUHF0Z332Pw" title="youtube.com">not happening</a> [youtube.com]?</p></div>
	</htmltext>
<tokenext>I just verified that it 's not currently happening .
I 'm in California if that matters.Me too .
I 'm also in CA and it is not curently happening.Are you saying this is currently not happening [ youtube.com ] ?</tokentext>
<sentencetext>I just verified that it's not currently happening.
I'm in California if that matters.Me too.
I'm also in CA and it is not curently happening.Are you saying this is currently not happening [youtube.com]?
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269215</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269817</id>
	<title>NAT box?</title>
	<author>bperkins</author>
	<datestamp>1244577600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I wonder if this could be caused by NAT boxes interfering with DNS.</p><p>I know my Netgear Wireless router does strange things with DNS requests but I never tried to verify what was going on.</p></htmltext>
<tokenext>I wonder if this could be caused by NAT boxes interfering with DNS.I know my Netgear Wireless router does strange things with DNS requests but I never tried to verify what was going on .</tokentext>
<sentencetext>I wonder if this could be caused by NAT boxes interfering with DNS.I know my Netgear Wireless router does strange things with DNS requests but I never tried to verify what was going on.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275981</id>
	<title>Re:Fuck `Em All</title>
	<author>Anonymous</author>
	<datestamp>1244575020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>Lars Ulrich evil?</htmltext>
<tokenext>Lars Ulrich evil ?</tokentext>
<sentencetext>Lars Ulrich evil?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28274663</id>
	<title>Verizon does this too</title>
	<author>Anonymous</author>
	<datestamp>1244563680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>If this makes you feel any better, Verizon also does this and none of us really care.</p></htmltext>
<tokenext>If this makes you feel any better , Verizon also does this and none of us really care .</tokentext>
<sentencetext>If this makes you feel any better, Verizon also does this and none of us really care.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272087</id>
	<title>Wide Open West has been doing this for years...</title>
	<author>Eggplant62</author>
	<datestamp>1244544180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Sorry this isn't re: Comcast, but I fired Comcast from providing my home cable service back in about 2003 since they wanted to put me on a NATted segment of their network on an RFC 1918 IP address. Ever since moving to Wide Open West, aka Wowway.com, traffic destined to my machine on port 53 from outside their network has been blocked. I don't pay extra for server connectivity, so I take my chances. Nevertheless, I've operated a hobby mail server sampling spam since being connected.</p></htmltext>
<tokenext>Sorry this is n't re : Comcast , but I fired Comcast from providing my home cable service back in about 2003 since they wanted to put me on a NATted segment of their network on an RFC 1918 IP address .
Ever since moving to Wide Open West , aka Wowway.com , traffic destined to my machine on port 53 from outside their network has been blocked .
I do n't pay extra for server connectivity , so I take my chances .
Nevertheless , I 've operated a hobby mail server sampling spam since being connected .</tokentext>
<sentencetext>Sorry this isn't re: Comcast, but I fired Comcast from providing my home cable service back in about 2003 since they wanted to put me on a NATted segment of their network on an RFC 1918 IP address.
Ever since moving to Wide Open West, aka Wowway.com, traffic destined to my machine on port 53 from outside their network has been blocked.
I don't pay extra for server connectivity, so I take my chances.
Nevertheless, I've operated a hobby mail server sampling spam since being connected.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269171</id>
	<title>Re:Fuck `Em All</title>
	<author>Anonymous</author>
	<datestamp>1244575320000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Scary fucking eeeeevil. Nazi evil.</p></div><p>Yes, because hijacking your DNS packets and injecting RST packets to interfere with bittorrent is comparable to putting millions of people in ovens and trying to conquer Eurasia.......</p></div>
	</htmltext>
<tokenext>Scary fucking eeeeevil .
Nazi evil.Yes , because hijacking your DNS packets and injecting RST packets to interfere with bittorrent is comparable to putting millions of people in ovens and trying to conquer Eurasia...... .</tokentext>
<sentencetext>Scary fucking eeeeevil.
Nazi evil.Yes, because hijacking your DNS packets and injecting RST packets to interfere with bittorrent is comparable to putting millions of people in ovens and trying to conquer Eurasia.......
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28274547</id>
	<title>Re:Is this happening for ANYONE?</title>
	<author>macbuzz01</author>
	<datestamp>1244562540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>so that's not my wife's emergency feminine hygiene product in my glove box?  Smart, very smart.</htmltext>
<tokenext>so that 's not my wife 's emergency feminine hygiene product in my glove box ?
Smart , very smart .</tokentext>
<sentencetext>so that's not my wife's emergency feminine hygiene product in my glove box?
Smart, very smart.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269435</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270425</id>
	<title>Re:Damn! That may stop my plan......</title>
	<author>Anonymous</author>
	<datestamp>1244579940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Sounds like you need port 80,81 or 8080.</p></htmltext>
<tokenext>Sounds like you need port 80,81 or 8080 .</tokentext>
<sentencetext>Sounds like you need port 80,81 or 8080.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269365</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270723</id>
	<title>Re:"Official Response"</title>
	<author>minerat</author>
	<datestamp>1244538000000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>Comcast has been using twitter for a while now, under the @ComcastCares account.  Multiple Comcast employees monitor twitter streams for complaints and are empowered to take action to resolve issues.  ComcastBonnie (as well as a few others) are authorized (cs? pr?) representatives for Comcast.  Given that her twitter page says the same thing as her post, you can probably take it at face value.</htmltext>
<tokenext>Comcast has been using twitter for a while now , under the @ ComcastCares account .
Multiple Comcast employees monitor twitter streams for complaints and are empowered to take action to resolve issues .
ComcastBonnie ( as well as a few others ) are authorized ( cs ?
pr ? ) representatives for Comcast .
Given that her twitter page says the same thing as her post , you can probably take it at face value .</tokentext>
<sentencetext>Comcast has been using twitter for a while now, under the @ComcastCares account.
Multiple Comcast employees monitor twitter streams for complaints and are empowered to take action to resolve issues.
ComcastBonnie (as well as a few others) are authorized (cs?
pr?) representatives for Comcast.
Given that her twitter page says the same thing as her post, you can probably take it at face value.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270179</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269627</id>
	<title>Re:I really am hoping this is NOT a gullibility te</title>
	<author>x78</author>
	<datestamp>1244576760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><a href="http://netalyzr.icsi.berkeley.edu/restore/id=4b65b8c9-17282-eef97e72-2eeb-4e02-bf77/" title="berkeley.edu" rel="nofollow">
You couldn't have just dropped the link?!</a> [berkeley.edu]</htmltext>
<tokenext>You could n't have just dropped the link ? !
[ berkeley.edu ]</tokentext>
<sentencetext>
You couldn't have just dropped the link?!
[berkeley.edu]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269115</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273189</id>
	<title>Re:Hmmm...</title>
	<author>fast turtle</author>
	<datestamp>1244551140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>TW's DNS service has been screwed up for the last 12 months at least, which is why I've been using OpenDNS though my router is configured with OpenDNS in Slot 1, TW in slot 2, OpenDNS slot 3 and TW in the final slot. Works nicely so far and I rarely hit the OpenDNS search page.</p></htmltext>
<tokenext>TW 's DNS service has been screwed up for the last 12 months at least , which is why I 've been using OpenDNS though my router is configured with OpenDNS in Slot 1 , TW in slot 2 , OpenDNS slot 3 and TW in the final slot .
Works nicely so far and I rarely hit the OpenDNS search page .</tokentext>
<sentencetext>TW's DNS service has been screwed up for the last 12 months at least, which is why I've been using OpenDNS though my router is configured with OpenDNS in Slot 1, TW in slot 2, OpenDNS slot 3 and TW in the final slot.
Works nicely so far and I rarely hit the OpenDNS search page.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269289</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270893</id>
	<title>Re:"Official Response"</title>
	<author>Anonymous</author>
	<datestamp>1244538840000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Troll moar.</p><p>Have you come out from under a rock and looked at the state of the internet in the last uh, 12 months? Did you miss the whole corporate Social Networking Explosion thing? Sorry. I'm totally trolling but w/e dude pay attention before you start talking. blol.</p></htmltext>
<tokenext>Troll moar.Have you come out from under a rock and looked at the state of the internet in the last uh , 12 months ?
Did you miss the whole corporate Social Networking Explosion thing ?
Sorry. I 'm totally trolling but w/e dude pay attention before you start talking .
blol .</tokentext>
<sentencetext>Troll moar.Have you come out from under a rock and looked at the state of the internet in the last uh, 12 months?
Did you miss the whole corporate Social Networking Explosion thing?
Sorry. I'm totally trolling but w/e dude pay attention before you start talking.
blol.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270179</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269581</id>
	<title>Re:Fuck `Em All</title>
	<author>sckeener</author>
	<datestamp>1244576580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I like to think of it as indifferent Evil vs Active Evil.

<p>Time Warner doesn't care about their customers (indifferent Evil)
</p><p>vs
</p><p>Comcast is out to get their customers. (Active Evil)

</p><p>another good way to describe them is....Time Warner is a Thief whereas Comcast is an Assassin.

</p><p>(I don't don't know who would be the Thief-Acrobat.  Which one's stock is fluctuating today?)</p></htmltext>
<tokenext>I like to think of it as indifferent Evil vs Active Evil .
Time Warner does n't care about their customers ( indifferent Evil ) vs Comcast is out to get their customers .
( Active Evil ) another good way to describe them is....Time Warner is a Thief whereas Comcast is an Assassin .
( I do n't do n't know who would be the Thief-Acrobat .
Which one 's stock is fluctuating today ?
)</tokentext>
<sentencetext>I like to think of it as indifferent Evil vs Active Evil.
Time Warner doesn't care about their customers (indifferent Evil)
vs
Comcast is out to get their customers.
(Active Evil)

another good way to describe them is....Time Warner is a Thief whereas Comcast is an Assassin.
(I don't don't know who would be the Thief-Acrobat.
Which one's stock is fluctuating today?
)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272125</id>
	<title>I strongly doubt this</title>
	<author>davidu</author>
	<datestamp>1244544420000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I run OpenDNS and we have about 12,000,000 end users.  A large number of those are comcast users.  We would know if this was true, and we haven't had a single report about it.</p><p>I also know a few<nobr> <wbr></nobr>/really smart/ people in the Comcast engineering department who run their DNS infrastructure. These guys wouldn't do something like block port 53.</p><p>Based on the above, there is no truth to this rumor from what I can tell and from those I've talked to.  I think an update on this story is warranted.</p><p>The comcast engineering team pride themselves on running a great network and robust infrastructure and I think they do a pretty good job (though of course I'm biased and think OpenDNS does a better job on the DNS side of the house)<nobr> <wbr></nobr>:-)</p><p>-David</p></htmltext>
<tokenext>I run OpenDNS and we have about 12,000,000 end users .
A large number of those are comcast users .
We would know if this was true , and we have n't had a single report about it.I also know a few /really smart/ people in the Comcast engineering department who run their DNS infrastructure .
These guys would n't do something like block port 53.Based on the above , there is no truth to this rumor from what I can tell and from those I 've talked to .
I think an update on this story is warranted.The comcast engineering team pride themselves on running a great network and robust infrastructure and I think they do a pretty good job ( though of course I 'm biased and think OpenDNS does a better job on the DNS side of the house ) : - ) -David</tokentext>
<sentencetext>I run OpenDNS and we have about 12,000,000 end users.
A large number of those are comcast users.
We would know if this was true, and we haven't had a single report about it.I also know a few /really smart/ people in the Comcast engineering department who run their DNS infrastructure.
These guys wouldn't do something like block port 53.Based on the above, there is no truth to this rumor from what I can tell and from those I've talked to.
I think an update on this story is warranted.The comcast engineering team pride themselves on running a great network and robust infrastructure and I think they do a pretty good job (though of course I'm biased and think OpenDNS does a better job on the DNS side of the house) :-)-David</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271081</id>
	<title>OpenDNS servers still ok from Colorado Comcast</title>
	<author>scum-o</author>
	<datestamp>1244539620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>[root@localhost ~]# nslookup slashdot.org<br>Server:         208.67.222.222<br>Address:        208.67.222.222#53</p><p>Non-authoritative answer:<br>Name:   slashdot.org<br>Address: 216.34.181.45</p></htmltext>
<tokenext>[ root @ localhost ~ ] # nslookup slashdot.orgServer : 208.67.222.222Address : 208.67.222.222 # 53Non-authoritative answer : Name : slashdot.orgAddress : 216.34.181.45</tokentext>
<sentencetext>[root@localhost ~]# nslookup slashdot.orgServer:         208.67.222.222Address:        208.67.222.222#53Non-authoritative answer:Name:   slashdot.orgAddress: 216.34.181.45</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28274567</id>
	<title>flawed diagnostics?</title>
	<author>GaryTorello</author>
	<datestamp>1244562660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>using Comcast in CT..  OpenDNS.org for DNS service..  works flawlessly.  Perhaps OP is the subject of a conspiracy targeting only him.</htmltext>
<tokenext>using Comcast in CT.. OpenDNS.org for DNS service.. works flawlessly .
Perhaps OP is the subject of a conspiracy targeting only him .</tokentext>
<sentencetext>using Comcast in CT..  OpenDNS.org for DNS service..  works flawlessly.
Perhaps OP is the subject of a conspiracy targeting only him.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272839</id>
	<title>Oh Boy</title>
	<author>DaMattster</author>
	<datestamp>1244548860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>This proof now that there is a need for a new internet and to go back to the mom and pop providers that don't pull all of this bull crap.  I miss the days of my small ISP where I could call them and get helpful, friendly tech support instead of having to navigate the myriad of voice prompts and CSRs that barely speak English.  I am all for the creation of new internet to go back to the ways of no regulation, no service tiering, and a completely neutral internet.</htmltext>
<tokenext>This proof now that there is a need for a new internet and to go back to the mom and pop providers that do n't pull all of this bull crap .
I miss the days of my small ISP where I could call them and get helpful , friendly tech support instead of having to navigate the myriad of voice prompts and CSRs that barely speak English .
I am all for the creation of new internet to go back to the ways of no regulation , no service tiering , and a completely neutral internet .</tokentext>
<sentencetext>This proof now that there is a need for a new internet and to go back to the mom and pop providers that don't pull all of this bull crap.
I miss the days of my small ISP where I could call them and get helpful, friendly tech support instead of having to navigate the myriad of voice prompts and CSRs that barely speak English.
I am all for the creation of new internet to go back to the ways of no regulation, no service tiering, and a completely neutral internet.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269147</id>
	<title>Security</title>
	<author>Anonymous</author>
	<datestamp>1244575200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>They could be doing this for security reasons, to prevent DNS domain hijacking.</p></htmltext>
<tokenext>They could be doing this for security reasons , to prevent DNS domain hijacking .</tokentext>
<sentencetext>They could be doing this for security reasons, to prevent DNS domain hijacking.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269271</id>
	<title>Re:Fuck `Em All</title>
	<author>Skye16</author>
	<datestamp>1244575620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Even Hitler started with baby steps</p></htmltext>
<tokenext>Even Hitler started with baby steps</tokentext>
<sentencetext>Even Hitler started with baby steps</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269171</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269531</id>
	<title>Official Response</title>
	<author>Anonymous</author>
	<datestamp>1244576400000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>4</modscore>
	<htmltext>Hey guys,

I just caught this on Twitter, and I can confirm that we do not and have not hijacked any DNS traffic in our network and certainly not to 3rd party resolvers. 'nuff said. I spoke with our DNS engineering folks, and they have confirmed.

If you would like to contact me, I'm @ComcastBonnie on Twitter.</htmltext>
<tokenext>Hey guys , I just caught this on Twitter , and I can confirm that we do not and have not hijacked any DNS traffic in our network and certainly not to 3rd party resolvers .
'nuff said .
I spoke with our DNS engineering folks , and they have confirmed .
If you would like to contact me , I 'm @ ComcastBonnie on Twitter .</tokentext>
<sentencetext>Hey guys,

I just caught this on Twitter, and I can confirm that we do not and have not hijacked any DNS traffic in our network and certainly not to 3rd party resolvers.
'nuff said.
I spoke with our DNS engineering folks, and they have confirmed.
If you would like to contact me, I'm @ComcastBonnie on Twitter.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28280795</id>
	<title>Re:Not happening to me</title>
	<author>digitalsushi</author>
	<datestamp>1244653620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I run public dns on a comcast dynamic ip.  I can usually go about 8 months without a re-lease giving me a new IP, so it's always been very acceptable.</p></htmltext>
<tokenext>I run public dns on a comcast dynamic ip .
I can usually go about 8 months without a re-lease giving me a new IP , so it 's always been very acceptable .</tokentext>
<sentencetext>I run public dns on a comcast dynamic ip.
I can usually go about 8 months without a re-lease giving me a new IP, so it's always been very acceptable.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269131</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269923</id>
	<title>Re:Port 53 Rerouted in Seattle :|</title>
	<author>stacysmomsmokesabong</author>
	<datestamp>1244578080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Hmm, it seems I'm one of maybe (just maybe...) two people who report 53 being re-routed. Perhaps it's a fluke on my end as I've been having VERY bad issues with the signal cutting out for hours at a time this week.<br>
<br>
I think I'm in agreement that the original article may not have been factual. I'll re-run my findings tonight (which is typically when the connection is most stable) and see what happens.</htmltext>
<tokenext>Hmm , it seems I 'm one of maybe ( just maybe... ) two people who report 53 being re-routed .
Perhaps it 's a fluke on my end as I 've been having VERY bad issues with the signal cutting out for hours at a time this week .
I think I 'm in agreement that the original article may not have been factual .
I 'll re-run my findings tonight ( which is typically when the connection is most stable ) and see what happens .</tokentext>
<sentencetext>Hmm, it seems I'm one of maybe (just maybe...) two people who report 53 being re-routed.
Perhaps it's a fluke on my end as I've been having VERY bad issues with the signal cutting out for hours at a time this week.
I think I'm in agreement that the original article may not have been factual.
I'll re-run my findings tonight (which is typically when the connection is most stable) and see what happens.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269633</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269295</id>
	<title>The scary part</title>
	<author>Anonymous</author>
	<datestamp>1244575740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>This practice effectively prohibits the use of alternative DNS roots, such as OpenNIC. In other words, it gives ICANN even stronger dominance over internet naming.</p></htmltext>
<tokenext>This practice effectively prohibits the use of alternative DNS roots , such as OpenNIC .
In other words , it gives ICANN even stronger dominance over internet naming .</tokentext>
<sentencetext>This practice effectively prohibits the use of alternative DNS roots, such as OpenNIC.
In other words, it gives ICANN even stronger dominance over internet naming.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28282141</id>
	<title>Re:Fuck `Em All</title>
	<author>Anonymous</author>
	<datestamp>1244658780000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>But.....they are comcastic....they commercial told me so.</p></htmltext>
<tokenext>But.....they are comcastic....they commercial told me so .</tokentext>
<sentencetext>But.....they are comcastic....they commercial told me so.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271685</id>
	<title>No problems in MS</title>
	<author>sdBlue</author>
	<datestamp>1244542440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I was originally Earthlink dialup (I lived in a VERY rural area in California), moved to Mississippi where it became TW.  TW got replaced about 2 years ago or so by Comcast.  My results appear clean:

DNS Tests

Restricted domain DNS lookup: OK
We are able to successfully lookup a name which resolves to the same IP address as our webserver. This means we are able to conduct many of the tests on your DNS server.

Unrestricted domain DNS lookup: OK
We are able to successfully lookup arbitrary names from within the Java applet. This means we are able to conduct all test on your DNS server.

DNS resolver address: OK
The IP address of your ISP's DNS Resolver is 68.87.74.165, which resolves to npls-cns03.bonitasprngs.fl.naples.comcast.net.

DNS resolver properties: Lookup latency: 170ms
Your ISP's DNS resolver requires 170 msec to conduct an external lookup.
Your resolver is using QTYPE=A for default queries.
Your resolver is not automatically performing IPv6 queries.
Your DNS resolver does not use EDNS.
Your resolver does not use 0x20 randomization, but will pass names in a case-sensitive manner.

DNS glue policy: OK
Your ISP's DNS resolver does not accept generic additional (glue) records &#226;" good.
Your ISP's DNS resolver does not accept additional (glue) records which correspond to nameservers.
Your ISP's DNS resolver does not follow CNAMEs.

DNS resolver port randomization: OK
Your ISP's DNS resolver properly randomizes its local port number.
The following graph shows DNS requests on the x-axis and the detected source ports on the y-axis.

port sequence plot

DNS lookups of popular domains: OK
74 of 74 popular names were resolved successfully. Show all names.
In the following table reverse lookups that failed but for which a Start Of Authority (SOA) entry indicated correct name associations are shown using an "X", followed by the SOA entry. Absence of both IP address and reverse name indicates failed forward lookups.
Name 	IP Address 	Reverse Name/SOA
www.abbey.co.uk 	165.160.15.20 	X (pdns1.cscdns.net)
ad.doubleclick.net 	209.62.176.153 	eqnjmegaadvip3.doubleclick.net
www.alliance-leicester.co.uk 	194.130.105.121 	X (alice.ioko365.com)
www.amazon.com 	72.21.207.65 	X (ddiamond.amazon.com)
www.ameritrade.com 	204.58.27.97 	beta-new.tdameritrade.com
www.bankofamerica.com 	171.159.65.173 	www.bankofamerica.com
www.bankofscotland.co.uk 	195.171.171.21 	X (ns0.bt.net)
www.bankofthewest.com 	207.114.194.101 	X (dns1a.bankofthewest.com)
www.barclays.co.uk 	213.219.1.141 	X (dns1.lon7.telecityredbus.net)
www.capitalone.com 	208.80.50.112 	X (chia.arin.NET)
www.careerbuilder.com 	208.82.5.22 	X (smokey.careerbuilder.com)
www.chase.com 	159.53.60.105 	X (ns1.jpmorganchase.com)
chaseonline.chase.com 	159.53.64.54 	resources-cdc2.chase.com
www.citi.com 	192.193.232.227 	X (ns.citicorp.com)
www.citibank.com 	192.193.217.200 	X (ns.citicorp.com)
www.citimortgage.com 	192.193.103.118 	X (ns.citicorp.com)
www.cnn.com 	157.166.226.25 	www.cnn.com
www.desjardins.com 	142.195.128.44 	desjardins.com
www.deutsche-bank.de 	217.73.49.24 	www.deutsche-bank.de
www.e-gold.com 	209.200.169.10 	unknown.prolexic.com
www.ebay.com 	66.135.200.145 	hp-core.ebay.com
www.etrade.com 	12.153.224.22 	etrade.com
www.f-secure.com 	96.17.74.131 	a96-17-74-131.d[...]echnologies.com
www.facebook.com 	69.63.184.31 	www-11-01-ash1.facebook.com
www.fdic.gov 	192.147.69.84 	www.fdic.gov
www.friendfinder.com 	208.88.180.81 	X (ii53-30.friendfinderinc.com)
www.geocities.com 	98.137.46.72 	intl1.geo.vip.sp2.yahoo.com
www.google.com 	209.85.165.99 	eo-in-f99.google.com
www.halifax.co.uk 	212.140.245.97 	halifax.co.uk
www.hsbc.co.uk 	193.108.74.126 	X (ns3.hsbc.com)
www.irs.gov 	96.17.75.10 	a96-17-75-10.de[...]echnologies.com
www.jpmorganchase.com 	159.53.60.166 	X (ns1.jpmorganchase.com)
www.lloydstsb.com 	193.34.230.181 	X (ns2.lloydstsb.co.uk)
mail.google.com 	209.85.165.18 	eo-in-f18.google.com
mail.live.com 	64.4.20.169 	dp2.mail.live.com
mail.yahoo.com 	209.191.92.114 	l2.login.vip.mud.yahoo.com
www.mbna.com 	209.135.59.10 	X (ns1.usi.net)
www.mbna.net 	209.135</htmltext>
<tokenext>I was originally Earthlink dialup ( I lived in a VERY rural area in California ) , moved to Mississippi where it became TW .
TW got replaced about 2 years ago or so by Comcast .
My results appear clean : DNS Tests Restricted domain DNS lookup : OK We are able to successfully lookup a name which resolves to the same IP address as our webserver .
This means we are able to conduct many of the tests on your DNS server .
Unrestricted domain DNS lookup : OK We are able to successfully lookup arbitrary names from within the Java applet .
This means we are able to conduct all test on your DNS server .
DNS resolver address : OK The IP address of your ISP 's DNS Resolver is 68.87.74.165 , which resolves to npls-cns03.bonitasprngs.fl.naples.comcast.net .
DNS resolver properties : Lookup latency : 170ms Your ISP 's DNS resolver requires 170 msec to conduct an external lookup .
Your resolver is using QTYPE = A for default queries .
Your resolver is not automatically performing IPv6 queries .
Your DNS resolver does not use EDNS .
Your resolver does not use 0x20 randomization , but will pass names in a case-sensitive manner .
DNS glue policy : OK Your ISP 's DNS resolver does not accept generic additional ( glue ) records   " good .
Your ISP 's DNS resolver does not accept additional ( glue ) records which correspond to nameservers .
Your ISP 's DNS resolver does not follow CNAMEs .
DNS resolver port randomization : OK Your ISP 's DNS resolver properly randomizes its local port number .
The following graph shows DNS requests on the x-axis and the detected source ports on the y-axis .
port sequence plot DNS lookups of popular domains : OK 74 of 74 popular names were resolved successfully .
Show all names .
In the following table reverse lookups that failed but for which a Start Of Authority ( SOA ) entry indicated correct name associations are shown using an " X " , followed by the SOA entry .
Absence of both IP address and reverse name indicates failed forward lookups .
Name IP Address Reverse Name/SOA www.abbey.co.uk 165.160.15.20 X ( pdns1.cscdns.net ) ad.doubleclick.net 209.62.176.153 eqnjmegaadvip3.doubleclick.net www.alliance-leicester.co.uk 194.130.105.121 X ( alice.ioko365.com ) www.amazon.com 72.21.207.65 X ( ddiamond.amazon.com ) www.ameritrade.com 204.58.27.97 beta-new.tdameritrade.com www.bankofamerica.com 171.159.65.173 www.bankofamerica.com www.bankofscotland.co.uk 195.171.171.21 X ( ns0.bt.net ) www.bankofthewest.com 207.114.194.101 X ( dns1a.bankofthewest.com ) www.barclays.co.uk 213.219.1.141 X ( dns1.lon7.telecityredbus.net ) www.capitalone.com 208.80.50.112 X ( chia.arin.NET ) www.careerbuilder.com 208.82.5.22 X ( smokey.careerbuilder.com ) www.chase.com 159.53.60.105 X ( ns1.jpmorganchase.com ) chaseonline.chase.com 159.53.64.54 resources-cdc2.chase.com www.citi.com 192.193.232.227 X ( ns.citicorp.com ) www.citibank.com 192.193.217.200 X ( ns.citicorp.com ) www.citimortgage.com 192.193.103.118 X ( ns.citicorp.com ) www.cnn.com 157.166.226.25 www.cnn.com www.desjardins.com 142.195.128.44 desjardins.com www.deutsche-bank.de 217.73.49.24 www.deutsche-bank.de www.e-gold.com 209.200.169.10 unknown.prolexic.com www.ebay.com 66.135.200.145 hp-core.ebay.com www.etrade.com 12.153.224.22 etrade.com www.f-secure.com 96.17.74.131 a96-17-74-131.d [ ... ] echnologies.com www.facebook.com 69.63.184.31 www-11-01-ash1.facebook.com www.fdic.gov 192.147.69.84 www.fdic.gov www.friendfinder.com 208.88.180.81 X ( ii53-30.friendfinderinc.com ) www.geocities.com 98.137.46.72 intl1.geo.vip.sp2.yahoo.com www.google.com 209.85.165.99 eo-in-f99.google.com www.halifax.co.uk 212.140.245.97 halifax.co.uk www.hsbc.co.uk 193.108.74.126 X ( ns3.hsbc.com ) www.irs.gov 96.17.75.10 a96-17-75-10.de [ ... ] echnologies.com www.jpmorganchase.com 159.53.60.166 X ( ns1.jpmorganchase.com ) www.lloydstsb.com 193.34.230.181 X ( ns2.lloydstsb.co.uk ) mail.google.com 209.85.165.18 eo-in-f18.google.com mail.live.com 64.4.20.169 dp2.mail.live.com mail.yahoo.com 209.191.92.114 l2.login.vip.mud.yahoo.com www.mbna.com 209.135.59.10 X ( ns1.usi.net ) www.mbna.net 209.135</tokentext>
<sentencetext>I was originally Earthlink dialup (I lived in a VERY rural area in California), moved to Mississippi where it became TW.
TW got replaced about 2 years ago or so by Comcast.
My results appear clean:

DNS Tests

Restricted domain DNS lookup: OK
We are able to successfully lookup a name which resolves to the same IP address as our webserver.
This means we are able to conduct many of the tests on your DNS server.
Unrestricted domain DNS lookup: OK
We are able to successfully lookup arbitrary names from within the Java applet.
This means we are able to conduct all test on your DNS server.
DNS resolver address: OK
The IP address of your ISP's DNS Resolver is 68.87.74.165, which resolves to npls-cns03.bonitasprngs.fl.naples.comcast.net.
DNS resolver properties: Lookup latency: 170ms
Your ISP's DNS resolver requires 170 msec to conduct an external lookup.
Your resolver is using QTYPE=A for default queries.
Your resolver is not automatically performing IPv6 queries.
Your DNS resolver does not use EDNS.
Your resolver does not use 0x20 randomization, but will pass names in a case-sensitive manner.
DNS glue policy: OK
Your ISP's DNS resolver does not accept generic additional (glue) records â" good.
Your ISP's DNS resolver does not accept additional (glue) records which correspond to nameservers.
Your ISP's DNS resolver does not follow CNAMEs.
DNS resolver port randomization: OK
Your ISP's DNS resolver properly randomizes its local port number.
The following graph shows DNS requests on the x-axis and the detected source ports on the y-axis.
port sequence plot

DNS lookups of popular domains: OK
74 of 74 popular names were resolved successfully.
Show all names.
In the following table reverse lookups that failed but for which a Start Of Authority (SOA) entry indicated correct name associations are shown using an "X", followed by the SOA entry.
Absence of both IP address and reverse name indicates failed forward lookups.
Name 	IP Address 	Reverse Name/SOA
www.abbey.co.uk 	165.160.15.20 	X (pdns1.cscdns.net)
ad.doubleclick.net 	209.62.176.153 	eqnjmegaadvip3.doubleclick.net
www.alliance-leicester.co.uk 	194.130.105.121 	X (alice.ioko365.com)
www.amazon.com 	72.21.207.65 	X (ddiamond.amazon.com)
www.ameritrade.com 	204.58.27.97 	beta-new.tdameritrade.com
www.bankofamerica.com 	171.159.65.173 	www.bankofamerica.com
www.bankofscotland.co.uk 	195.171.171.21 	X (ns0.bt.net)
www.bankofthewest.com 	207.114.194.101 	X (dns1a.bankofthewest.com)
www.barclays.co.uk 	213.219.1.141 	X (dns1.lon7.telecityredbus.net)
www.capitalone.com 	208.80.50.112 	X (chia.arin.NET)
www.careerbuilder.com 	208.82.5.22 	X (smokey.careerbuilder.com)
www.chase.com 	159.53.60.105 	X (ns1.jpmorganchase.com)
chaseonline.chase.com 	159.53.64.54 	resources-cdc2.chase.com
www.citi.com 	192.193.232.227 	X (ns.citicorp.com)
www.citibank.com 	192.193.217.200 	X (ns.citicorp.com)
www.citimortgage.com 	192.193.103.118 	X (ns.citicorp.com)
www.cnn.com 	157.166.226.25 	www.cnn.com
www.desjardins.com 	142.195.128.44 	desjardins.com
www.deutsche-bank.de 	217.73.49.24 	www.deutsche-bank.de
www.e-gold.com 	209.200.169.10 	unknown.prolexic.com
www.ebay.com 	66.135.200.145 	hp-core.ebay.com
www.etrade.com 	12.153.224.22 	etrade.com
www.f-secure.com 	96.17.74.131 	a96-17-74-131.d[...]echnologies.com
www.facebook.com 	69.63.184.31 	www-11-01-ash1.facebook.com
www.fdic.gov 	192.147.69.84 	www.fdic.gov
www.friendfinder.com 	208.88.180.81 	X (ii53-30.friendfinderinc.com)
www.geocities.com 	98.137.46.72 	intl1.geo.vip.sp2.yahoo.com
www.google.com 	209.85.165.99 	eo-in-f99.google.com
www.halifax.co.uk 	212.140.245.97 	halifax.co.uk
www.hsbc.co.uk 	193.108.74.126 	X (ns3.hsbc.com)
www.irs.gov 	96.17.75.10 	a96-17-75-10.de[...]echnologies.com
www.jpmorganchase.com 	159.53.60.166 	X (ns1.jpmorganchase.com)
www.lloydstsb.com 	193.34.230.181 	X (ns2.lloydstsb.co.uk)
mail.google.com 	209.85.165.18 	eo-in-f18.google.com
mail.live.com 	64.4.20.169 	dp2.mail.live.com
mail.yahoo.com 	209.191.92.114 	l2.login.vip.mud.yahoo.com
www.mbna.com 	209.135.59.10 	X (ns1.usi.net)
www.mbna.net 	209.135</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272267</id>
	<title>Re:Fuck `Em All</title>
	<author>Anonymous</author>
	<datestamp>1244545080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>All your medias are belong to us!</p></htmltext>
<tokenext>All your medias are belong to us !</tokentext>
<sentencetext>All your medias are belong to us!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272927</id>
	<title>Re:If you want real Comcast fun...</title>
	<author>Anonymous</author>
	<datestamp>1244549460000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>You don't understand how DNS works (or TCP/IP, for that matter).</p></htmltext>
<tokenext>You do n't understand how DNS works ( or TCP/IP , for that matter ) .</tokentext>
<sentencetext>You don't understand how DNS works (or TCP/IP, for that matter).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269263</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269397</id>
	<title>OpenDNS</title>
	<author>Clipless</author>
	<datestamp>1244575920000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>A good friend of mine was using OpenDNS on Comcast and one day, without warning, his internet service was cut off.<br>When he called the phone rep said that Comcast had disabled his internet because he was not using their DNS server and that if he wanted to have Comcast as a provider he had no choice but to use DNS servers provided by DHCP!</p></htmltext>
<tokenext>A good friend of mine was using OpenDNS on Comcast and one day , without warning , his internet service was cut off.When he called the phone rep said that Comcast had disabled his internet because he was not using their DNS server and that if he wanted to have Comcast as a provider he had no choice but to use DNS servers provided by DHCP !</tokentext>
<sentencetext>A good friend of mine was using OpenDNS on Comcast and one day, without warning, his internet service was cut off.When he called the phone rep said that Comcast had disabled his internet because he was not using their DNS server and that if he wanted to have Comcast as a provider he had no choice but to use DNS servers provided by DHCP!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28274065</id>
	<title>Cox DNS TTLs</title>
	<author>heypete</author>
	<datestamp>1244558280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>While we're on the topic of DNS, could someone please tell the DNS folks at Cox Cable that it's really rude to arbitrarily rewrite all TTLs to 30 seconds.</p><p>There's a reason why some people set their TTLs to higher than 30 seconds. Fortunately, I have my DD-WRT box set to use OpenDNS' resolvers, which work well.</p><p>All of my attempts to inform Cox of their TTL issue have met with responses like "We've received your email regarding your difficulties in configuring your wireless router at home. Here's some instructions for configuring your wireless router..." even when I don't mention anything about a wireless network.</p></htmltext>
<tokenext>While we 're on the topic of DNS , could someone please tell the DNS folks at Cox Cable that it 's really rude to arbitrarily rewrite all TTLs to 30 seconds.There 's a reason why some people set their TTLs to higher than 30 seconds .
Fortunately , I have my DD-WRT box set to use OpenDNS ' resolvers , which work well.All of my attempts to inform Cox of their TTL issue have met with responses like " We 've received your email regarding your difficulties in configuring your wireless router at home .
Here 's some instructions for configuring your wireless router... " even when I do n't mention anything about a wireless network .</tokentext>
<sentencetext>While we're on the topic of DNS, could someone please tell the DNS folks at Cox Cable that it's really rude to arbitrarily rewrite all TTLs to 30 seconds.There's a reason why some people set their TTLs to higher than 30 seconds.
Fortunately, I have my DD-WRT box set to use OpenDNS' resolvers, which work well.All of my attempts to inform Cox of their TTL issue have met with responses like "We've received your email regarding your difficulties in configuring your wireless router at home.
Here's some instructions for configuring your wireless router..." even when I don't mention anything about a wireless network.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271727</id>
	<title>Charter Cable In St. Louis</title>
	<author>Anonymous</author>
	<datestamp>1244542620000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Direct UDP access to remote MSSQL servers (port 1434) is blocked.<br>This is most likely due to a filtering rule against the Slammer worm</p><p>Direct TCP access to remote SMTP servers (port 25) succeeds, but does not return the expected content.</p><p>Direct TCP connections to remote POP servers (port 110) succeed, but do not receive the expected content.</p><p>Direct TCP connections to remote IMAP servers (port 143) succeed, but do not receive the expected content.</p><p>Your ISP's DNS server returns IP addresses even for domain names which should not resolve. Instead of an error, the DNS server returns an address of 63.251.179.56, which does not resolve. You can inspect the resulting HTML content here.</p><p>And people were worried about comcast messing with their stuff</p></htmltext>
<tokenext>Direct UDP access to remote MSSQL servers ( port 1434 ) is blocked.This is most likely due to a filtering rule against the Slammer wormDirect TCP access to remote SMTP servers ( port 25 ) succeeds , but does not return the expected content.Direct TCP connections to remote POP servers ( port 110 ) succeed , but do not receive the expected content.Direct TCP connections to remote IMAP servers ( port 143 ) succeed , but do not receive the expected content.Your ISP 's DNS server returns IP addresses even for domain names which should not resolve .
Instead of an error , the DNS server returns an address of 63.251.179.56 , which does not resolve .
You can inspect the resulting HTML content here.And people were worried about comcast messing with their stuff</tokentext>
<sentencetext>Direct UDP access to remote MSSQL servers (port 1434) is blocked.This is most likely due to a filtering rule against the Slammer wormDirect TCP access to remote SMTP servers (port 25) succeeds, but does not return the expected content.Direct TCP connections to remote POP servers (port 110) succeed, but do not receive the expected content.Direct TCP connections to remote IMAP servers (port 143) succeed, but do not receive the expected content.Your ISP's DNS server returns IP addresses even for domain names which should not resolve.
Instead of an error, the DNS server returns an address of 63.251.179.56, which does not resolve.
You can inspect the resulting HTML content here.And people were worried about comcast messing with their stuff</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270943</id>
	<title>Re:Security</title>
	<author>Anonymous</author>
	<datestamp>1244539020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>You can't be serious?  What are you the PR guy for Comcast?!</p></htmltext>
<tokenext>You ca n't be serious ?
What are you the PR guy for Comcast ?
!</tokentext>
<sentencetext>You can't be serious?
What are you the PR guy for Comcast?
!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269147</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28298337</id>
	<title>Thanks!</title>
	<author>Anonymous</author>
	<datestamp>1244751120000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Thanks for the heads up on the link: comcastisfuckingwithyourport53traffic.wordpress.com.  I should be getting a call from IT-Security any minute now...</p></htmltext>
<tokenext>Thanks for the heads up on the link : comcastisfuckingwithyourport53traffic.wordpress.com .
I should be getting a call from IT-Security any minute now.. .</tokentext>
<sentencetext>Thanks for the heads up on the link: comcastisfuckingwithyourport53traffic.wordpress.com.
I should be getting a call from IT-Security any minute now...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271973</id>
	<title>How To Beta Test Your Software, the Slashdot Way</title>
	<author>damn\_registrars</author>
	<datestamp>1244543760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Sure, you could follow "traditional" measure of beta testing your software, but what fun is that?  Try the Slashdot Method(TM) instead, and launch your beta testing into the next level!  Just follow our easy step-by-step instructions<ul> <li> <b>First</b>:  Make a plausible-sounding claim about a company people don't like (cable, MS, RIAA, telco, etc)</li><li> <b>Second</b>:  Claim that your software can help diagnose these problems</li><li> <b>Third</b>:  Watch as suckers from all over the world download your new program</li><li> <b>Fourth</b>:  When the truth happens that your claim holds less water than a screen door, point out that your software helped show that, and was never supposed to fix anything anyways</li><li> <b>Fifth</b>:  Point out that you still do a better job beta-testing before release than <a href="http://slashdot.org/" title="slashdot.org">these guys</a> [slashdot.org] </li><li> <b>Sixth</b>: Do <a href="http://www.youtube.com/watch?v=oHg5SJYRHA0" title="youtube.com">a happy dance</a> [youtube.com] </li><li> <b>Seventh</b>: </li><li> <b>Eighth</b>: Profit!</li></ul></htmltext>
<tokenext>Sure , you could follow " traditional " measure of beta testing your software , but what fun is that ?
Try the Slashdot Method ( TM ) instead , and launch your beta testing into the next level !
Just follow our easy step-by-step instructions First : Make a plausible-sounding claim about a company people do n't like ( cable , MS , RIAA , telco , etc ) Second : Claim that your software can help diagnose these problems Third : Watch as suckers from all over the world download your new program Fourth : When the truth happens that your claim holds less water than a screen door , point out that your software helped show that , and was never supposed to fix anything anyways Fifth : Point out that you still do a better job beta-testing before release than these guys [ slashdot.org ] Sixth : Do a happy dance [ youtube.com ] Seventh : Eighth : Profit !</tokentext>
<sentencetext>Sure, you could follow "traditional" measure of beta testing your software, but what fun is that?
Try the Slashdot Method(TM) instead, and launch your beta testing into the next level!
Just follow our easy step-by-step instructions  First:  Make a plausible-sounding claim about a company people don't like (cable, MS, RIAA, telco, etc) Second:  Claim that your software can help diagnose these problems Third:  Watch as suckers from all over the world download your new program Fourth:  When the truth happens that your claim holds less water than a screen door, point out that your software helped show that, and was never supposed to fix anything anyways Fifth:  Point out that you still do a better job beta-testing before release than these guys [slashdot.org]  Sixth: Do a happy dance [youtube.com]  Seventh:  Eighth: Profit!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269563</id>
	<title>As one of the authors of Netalyzr...</title>
	<author>Anonymous</author>
	<datestamp>1244576520000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p>We have not seen any redirection issues with Comcast user's DNS settings.</p><p>Questions on netalyzr itself will be answered in this thread.</p></htmltext>
<tokenext>We have not seen any redirection issues with Comcast user 's DNS settings.Questions on netalyzr itself will be answered in this thread .</tokentext>
<sentencetext>We have not seen any redirection issues with Comcast user's DNS settings.Questions on netalyzr itself will be answered in this thread.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272469</id>
	<title>Open DNS</title>
	<author>r6\_jason</author>
	<datestamp>1244546640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><a href="http://netalyzr.icsi.berkeley.edu/restore/id=ae8199ad-23094-f50550b1-c25f-4332-87fe" title="berkeley.edu" rel="nofollow">http://netalyzr.icsi.berkeley.edu/restore/id=ae8199ad-23094-f50550b1-c25f-4332-87fe</a> [berkeley.edu]

Seems like OpenDNS is working OK for me.</htmltext>
<tokenext>http : //netalyzr.icsi.berkeley.edu/restore/id = ae8199ad-23094-f50550b1-c25f-4332-87fe [ berkeley.edu ] Seems like OpenDNS is working OK for me .</tokentext>
<sentencetext>http://netalyzr.icsi.berkeley.edu/restore/id=ae8199ad-23094-f50550b1-c25f-4332-87fe [berkeley.edu]

Seems like OpenDNS is working OK for me.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269771</id>
	<title>Re:That's a negative</title>
	<author>Anonymous</author>
	<datestamp>1244577420000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>If you read the article and understood the tests he performed, you'd know this wasn't the case.</p></htmltext>
<tokenext>If you read the article and understood the tests he performed , you 'd know this was n't the case .</tokentext>
<sentencetext>If you read the article and understood the tests he performed, you'd know this wasn't the case.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269093</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270953</id>
	<title>What's the big deal?</title>
	<author>Pictish Prince</author>
	<datestamp>1244539080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>All of us power users have all the IPs memorized.</htmltext>
<tokenext>All of us power users have all the IPs memorized .</tokentext>
<sentencetext>All of us power users have all the IPs memorized.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271813</id>
	<title>Re:Not happening to me</title>
	<author>sjames</author>
	<datestamp>1244543040000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Earlier today, I was changing nameservers for a domain. In preparation, I configured my nameserver with a zonefile containing the new IP addresses for that domain, but did not change the NS records at the registrar. I then used dig from home to query my DNS directly and got the new IPs, not what the authoritative nameservers would return.</p><p>Naturally after I was satisfied that the zone file was correct, I changed the ns records for the domain.</p></htmltext>
<tokenext>Earlier today , I was changing nameservers for a domain .
In preparation , I configured my nameserver with a zonefile containing the new IP addresses for that domain , but did not change the NS records at the registrar .
I then used dig from home to query my DNS directly and got the new IPs , not what the authoritative nameservers would return.Naturally after I was satisfied that the zone file was correct , I changed the ns records for the domain .</tokentext>
<sentencetext>Earlier today, I was changing nameservers for a domain.
In preparation, I configured my nameserver with a zonefile containing the new IP addresses for that domain, but did not change the NS records at the registrar.
I then used dig from home to query my DNS directly and got the new IPs, not what the authoritative nameservers would return.Naturally after I was satisfied that the zone file was correct, I changed the ns records for the domain.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269251</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28274779</id>
	<title>Can't test it.</title>
	<author>shentino</author>
	<datestamp>1244564520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>My college is blocking outbound port 53</p></htmltext>
<tokenext>My college is blocking outbound port 53</tokentext>
<sentencetext>My college is blocking outbound port 53</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269573</id>
	<title>So let me see if I have this straight...</title>
	<author>BaronHethorSamedi</author>
	<datestamp>1244576580000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext>An anonymous reader submits a "story" linking to a random blog spouting off rumors about a nefarious scheme by Comcast to redirect port traffic.  The "story" is then published under a headline asserting the rumor as fact, while the summary is actually a plea for the fact-checking on the story to be done by readers.<br>
<br>
News for nerds, indeed.</htmltext>
<tokenext>An anonymous reader submits a " story " linking to a random blog spouting off rumors about a nefarious scheme by Comcast to redirect port traffic .
The " story " is then published under a headline asserting the rumor as fact , while the summary is actually a plea for the fact-checking on the story to be done by readers .
News for nerds , indeed .</tokentext>
<sentencetext>An anonymous reader submits a "story" linking to a random blog spouting off rumors about a nefarious scheme by Comcast to redirect port traffic.
The "story" is then published under a headline asserting the rumor as fact, while the summary is actually a plea for the fact-checking on the story to be done by readers.
News for nerds, indeed.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269481</id>
	<title>Re:Not happening to me</title>
	<author>whoever57</author>
	<datestamp>1244576220000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>5</modscore>
	<htmltext><blockquote><div><p>Are you certain? If they are redirecting the traffic in their network so that one of their DNS servers responds to the query  as if  it was your DNS server</p></div></blockquote><p>

I'm certain. I sent a query to a DNS server that I control. I ran tcpdump on the DNS server and I could see the packets from my home IP address coming in with the query and the refusal going out (I asked the DNS server that I control to resolve yahoo.com, which it should refuse to do).</p></div>
	</htmltext>
<tokenext>Are you certain ?
If they are redirecting the traffic in their network so that one of their DNS servers responds to the query as if it was your DNS server I 'm certain .
I sent a query to a DNS server that I control .
I ran tcpdump on the DNS server and I could see the packets from my home IP address coming in with the query and the refusal going out ( I asked the DNS server that I control to resolve yahoo.com , which it should refuse to do ) .</tokentext>
<sentencetext>Are you certain?
If they are redirecting the traffic in their network so that one of their DNS servers responds to the query  as if  it was your DNS server

I'm certain.
I sent a query to a DNS server that I control.
I ran tcpdump on the DNS server and I could see the packets from my home IP address coming in with the query and the refusal going out (I asked the DNS server that I control to resolve yahoo.com, which it should refuse to do).
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269251</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269795</id>
	<title>nslookup www.google.com flibitteyglibbit.com</title>
	<author>goffster</author>
	<datestamp>1244577480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>look at that...  it still worked.</p><p>I wonder if comcast decided to server your request when it could not resolve your dns server?</p></htmltext>
<tokenext>look at that... it still worked.I wonder if comcast decided to server your request when it could not resolve your dns server ?</tokentext>
<sentencetext>look at that...  it still worked.I wonder if comcast decided to server your request when it could not resolve your dns server?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270739</id>
	<title>Re:Fuck `Em All</title>
	<author>Anonymous</author>
	<datestamp>1244538060000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Correction: Time Warner Cable is a separate entity from Time Warner. Also, Warner Music is no longer a part of Time Warner as well.</p></htmltext>
<tokenext>Correction : Time Warner Cable is a separate entity from Time Warner .
Also , Warner Music is no longer a part of Time Warner as well .</tokentext>
<sentencetext>Correction: Time Warner Cable is a separate entity from Time Warner.
Also, Warner Music is no longer a part of Time Warner as well.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269301</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269093</id>
	<title>That's a negative</title>
	<author>jjb3rd</author>
	<datestamp>1244575080000</datestamp>
	<modclass>Funny</modclass>
	<modscore>5</modscore>
	<htmltext>I'm a comcast user and it works for me...perhaps his home network is the problem.  A Linux user having a misconfigured network?!??!  Oh wait this is Slashdot...nevermind.</htmltext>
<tokenext>I 'm a comcast user and it works for me...perhaps his home network is the problem .
A Linux user having a misconfigured network ? ! ? ? !
Oh wait this is Slashdot...nevermind .</tokentext>
<sentencetext>I'm a comcast user and it works for me...perhaps his home network is the problem.
A Linux user having a misconfigured network?!??!
Oh wait this is Slashdot...nevermind.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273929</id>
	<title>Posting your IP address</title>
	<author>Anonymous</author>
	<datestamp>1244556960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>it's really sad that, not only are Slashdotters foolish enough to post a results page with their own IP in them, but also that the advice to do so was given by a Slashdot editor!</p><p>We've been modded as Flamebait for months when criticizing this guy but... but I mean....really? REALLY? *facepalm*</p><p>If I was a subscriber, I'd be canceling. Taco should be pissed, and you should be ashamed of yourselves for posting those Netalyzr direct URLs unless you're testing from a business with a public IP address; and really if we're talking about Comcast home accounts, what good is that?</p></htmltext>
<tokenext>it 's really sad that , not only are Slashdotters foolish enough to post a results page with their own IP in them , but also that the advice to do so was given by a Slashdot editor ! We 've been modded as Flamebait for months when criticizing this guy but... but I mean....really ?
REALLY ? * facepalm * If I was a subscriber , I 'd be canceling .
Taco should be pissed , and you should be ashamed of yourselves for posting those Netalyzr direct URLs unless you 're testing from a business with a public IP address ; and really if we 're talking about Comcast home accounts , what good is that ?</tokentext>
<sentencetext>it's really sad that, not only are Slashdotters foolish enough to post a results page with their own IP in them, but also that the advice to do so was given by a Slashdot editor!We've been modded as Flamebait for months when criticizing this guy but... but I mean....really?
REALLY? *facepalm*If I was a subscriber, I'd be canceling.
Taco should be pissed, and you should be ashamed of yourselves for posting those Netalyzr direct URLs unless you're testing from a business with a public IP address; and really if we're talking about Comcast home accounts, what good is that?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270499</id>
	<title>Re:Fuck `Em All</title>
	<author>Tokerat</author>
	<datestamp>1244580240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It's funny because Comcast has been the most reliable ISP I've ever had. I've had torrents hit 2MB/Sec (not a typo, that's Megabytes), although not sustained. The only problem was when they came to disconnect another apartment in my building and they pulled the plug on me by accident - the fault of the stupid installer guy. Took them a few days to turn it back on which sucked, but I never get over-billed, and it always just works.</p><p>Then I saw their commercials with the chick singing in a monotone about "Always dreaming, never stopping" and boy, do I agree with you.</p></htmltext>
<tokenext>It 's funny because Comcast has been the most reliable ISP I 've ever had .
I 've had torrents hit 2MB/Sec ( not a typo , that 's Megabytes ) , although not sustained .
The only problem was when they came to disconnect another apartment in my building and they pulled the plug on me by accident - the fault of the stupid installer guy .
Took them a few days to turn it back on which sucked , but I never get over-billed , and it always just works.Then I saw their commercials with the chick singing in a monotone about " Always dreaming , never stopping " and boy , do I agree with you .</tokentext>
<sentencetext>It's funny because Comcast has been the most reliable ISP I've ever had.
I've had torrents hit 2MB/Sec (not a typo, that's Megabytes), although not sustained.
The only problem was when they came to disconnect another apartment in my building and they pulled the plug on me by accident - the fault of the stupid installer guy.
Took them a few days to turn it back on which sucked, but I never get over-billed, and it always just works.Then I saw their commercials with the chick singing in a monotone about "Always dreaming, never stopping" and boy, do I agree with you.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269161</id>
	<title>Doesn't happen for me</title>
	<author>nedlohs</author>
	<datestamp>1244575260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>with comcast in NJ.</p><p>Thn again I don't get advertising page IPs in response to non-existant names either.</p></htmltext>
<tokenext>with comcast in NJ.Thn again I do n't get advertising page IPs in response to non-existant names either .</tokentext>
<sentencetext>with comcast in NJ.Thn again I don't get advertising page IPs in response to non-existant names either.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272953</id>
	<title>reply, ran the analyzer</title>
	<author>Anonymous</author>
	<datestamp>1244549640000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>c-24-0-249-85.hsd1.pa.comcast.net / 24.0.249.85</p><p>http://n17.netalyzr.icsi.berkeley.edu/summary/id=43ca3cda-24640-2921bc58-01af-4d27-a12e</p><p>is the permalink for me from that test.</p><p>I think hahaha.   I used to be big into computers, not so much anymore.</p><p>That's what pre-med'll do to you.</p><p>K. Holland</p><p>kt.holla1@gmail.com</p></htmltext>
<tokenext>c-24-0-249-85.hsd1.pa.comcast.net / 24.0.249.85http : //n17.netalyzr.icsi.berkeley.edu/summary/id = 43ca3cda-24640-2921bc58-01af-4d27-a12eis the permalink for me from that test.I think hahaha .
I used to be big into computers , not so much anymore.That 's what pre-med 'll do to you.K .
Hollandkt.holla1 @ gmail.com</tokentext>
<sentencetext>c-24-0-249-85.hsd1.pa.comcast.net / 24.0.249.85http://n17.netalyzr.icsi.berkeley.edu/summary/id=43ca3cda-24640-2921bc58-01af-4d27-a12eis the permalink for me from that test.I think hahaha.
I used to be big into computers, not so much anymore.That's what pre-med'll do to you.K.
Hollandkt.holla1@gmail.com</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269129</id>
	<title>Using OpenDNS here</title>
	<author>rpmonkey</author>
	<datestamp>1244575200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I switched my DNS to OpenDNS because Comcast's DNS servers were unreliable for me. I am definitely hitting OpenDNS because if I typo a domain I'm redirected to the OpenDNS guide page. I'm a Northern California Comcast user.</htmltext>
<tokenext>I switched my DNS to OpenDNS because Comcast 's DNS servers were unreliable for me .
I am definitely hitting OpenDNS because if I typo a domain I 'm redirected to the OpenDNS guide page .
I 'm a Northern California Comcast user .</tokentext>
<sentencetext>I switched my DNS to OpenDNS because Comcast's DNS servers were unreliable for me.
I am definitely hitting OpenDNS because if I typo a domain I'm redirected to the OpenDNS guide page.
I'm a Northern California Comcast user.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269253</id>
	<title>Re:Fuck `Em All</title>
	<author>Itninja</author>
	<datestamp>1244575560000</datestamp>
	<modclass>Funny</modclass>
	<modscore>4</modscore>
	<htmltext>I think the parent was just using a bit of hyperbole there. Also, it appears he only has a limited understanding of what the word 'evil' means. And the word 'fuck'. And, well, he just don't appear to be that bright in general.</htmltext>
<tokenext>I think the parent was just using a bit of hyperbole there .
Also , it appears he only has a limited understanding of what the word 'evil ' means .
And the word 'fuck' .
And , well , he just do n't appear to be that bright in general .</tokentext>
<sentencetext>I think the parent was just using a bit of hyperbole there.
Also, it appears he only has a limited understanding of what the word 'evil' means.
And the word 'fuck'.
And, well, he just don't appear to be that bright in general.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269171</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269895</id>
	<title>I hate comcast more then most... but..</title>
	<author>Anonymous</author>
	<datestamp>1244577960000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>First, I hate comcast. I have a lot of reasons to hate comcast. I wish they would just go away. their service sucks, their support sucks, and well if they wanted to suck<nobr> <wbr></nobr>.... I would be worried about the horrible deadly diseases they would carry.</p><p>Anyways. I understand for the geek this sucks, but for the average home user, I think this is a good thing. How many less computers will be hijacked due to not being redirected to some rogue site? How many clueless people will not give up their bank account information to scammers because their dns couldn't be redirected?</p><p>I believe this is a necessary evil. I believe if they were doing it for legitimate reasons, they should have a choice to opt out for those in the clue.</p><p>Unfortunately as scammers/crackers(btw.. WTF? crackers? all scum bags who crack computers are white? What?<nobr> <wbr></nobr>:P) etc escalate because more and more retards are getting on the internet without having a clue how to protect themselves, this is going to become more and more of a norm.. isps "trying to protect you from yourself".</p><p>Think of it as getting a ticket for not wearing a seat belt. Supposedly it's to protect you from yourself.. but in reality it is to earn more money, and take away your control over your life.</p><p>Let the flamebait flow!</p></htmltext>
<tokenext>First , I hate comcast .
I have a lot of reasons to hate comcast .
I wish they would just go away .
their service sucks , their support sucks , and well if they wanted to suck .... I would be worried about the horrible deadly diseases they would carry.Anyways .
I understand for the geek this sucks , but for the average home user , I think this is a good thing .
How many less computers will be hijacked due to not being redirected to some rogue site ?
How many clueless people will not give up their bank account information to scammers because their dns could n't be redirected ? I believe this is a necessary evil .
I believe if they were doing it for legitimate reasons , they should have a choice to opt out for those in the clue.Unfortunately as scammers/crackers ( btw.. WTF ? crackers ?
all scum bags who crack computers are white ?
What ? : P ) etc escalate because more and more retards are getting on the internet without having a clue how to protect themselves , this is going to become more and more of a norm.. isps " trying to protect you from yourself " .Think of it as getting a ticket for not wearing a seat belt .
Supposedly it 's to protect you from yourself.. but in reality it is to earn more money , and take away your control over your life.Let the flamebait flow !</tokentext>
<sentencetext>First, I hate comcast.
I have a lot of reasons to hate comcast.
I wish they would just go away.
their service sucks, their support sucks, and well if they wanted to suck .... I would be worried about the horrible deadly diseases they would carry.Anyways.
I understand for the geek this sucks, but for the average home user, I think this is a good thing.
How many less computers will be hijacked due to not being redirected to some rogue site?
How many clueless people will not give up their bank account information to scammers because their dns couldn't be redirected?I believe this is a necessary evil.
I believe if they were doing it for legitimate reasons, they should have a choice to opt out for those in the clue.Unfortunately as scammers/crackers(btw.. WTF? crackers?
all scum bags who crack computers are white?
What? :P) etc escalate because more and more retards are getting on the internet without having a clue how to protect themselves, this is going to become more and more of a norm.. isps "trying to protect you from yourself".Think of it as getting a ticket for not wearing a seat belt.
Supposedly it's to protect you from yourself.. but in reality it is to earn more money, and take away your control over your life.Let the flamebait flow!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270349</id>
	<title>Not in NE Massachusetts...</title>
	<author>Anonymous</author>
	<datestamp>1244579640000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>(Comcast, North of Boston)</p></htmltext>
<tokenext>( Comcast , North of Boston )</tokentext>
<sentencetext>(Comcast, North of Boston)</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269813</id>
	<title>business or home comcast?</title>
	<author>MoFoQ</author>
	<datestamp>1244577600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I wonder if a business class versus a home/residential version of Comcast service makes a difference.<br>And which one the guy used?</p></htmltext>
<tokenext>I wonder if a business class versus a home/residential version of Comcast service makes a difference.And which one the guy used ?</tokentext>
<sentencetext>I wonder if a business class versus a home/residential version of Comcast service makes a difference.And which one the guy used?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269181</id>
	<title>Re:Fuck `Em All</title>
	<author>Anonymous</author>
	<datestamp>1244575320000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext><p>That's the quickest Godwin proof I've seen in a while.</p></htmltext>
<tokenext>That 's the quickest Godwin proof I 've seen in a while .</tokentext>
<sentencetext>That's the quickest Godwin proof I've seen in a while.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269263</id>
	<title>If you want real Comcast fun...</title>
	<author>NecroPuppy</author>
	<datestamp>1244575560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Take a look at the packet loss on their Augusta, GA servers.  Regularly, from 10 PM to 1 AM (or later), 50\%+ packet loss.</p><p>I know because a buddy's radio show keeps crapping out, and it goes through there.  But when I rebroadcast the show as a test (and don't go through that server), the issues don't happen.</p><p>But their L1 and L2 techs can't figure out the problem.</p></htmltext>
<tokenext>Take a look at the packet loss on their Augusta , GA servers .
Regularly , from 10 PM to 1 AM ( or later ) , 50 \ % + packet loss.I know because a buddy 's radio show keeps crapping out , and it goes through there .
But when I rebroadcast the show as a test ( and do n't go through that server ) , the issues do n't happen.But their L1 and L2 techs ca n't figure out the problem .</tokentext>
<sentencetext>Take a look at the packet loss on their Augusta, GA servers.
Regularly, from 10 PM to 1 AM (or later), 50\%+ packet loss.I know because a buddy's radio show keeps crapping out, and it goes through there.
But when I rebroadcast the show as a test (and don't go through that server), the issues don't happen.But their L1 and L2 techs can't figure out the problem.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269613</id>
	<title>As most of you may have noticed by now....</title>
	<author>Anonymous</author>
	<datestamp>1244576700000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Comcast does not intercept port 53.  A check using Netalyzer from ICSI or running a dig or nslookup will validate this for you against any third party resolver or any of the Comcast DNS servers.</p><p>This is just plain old FUD.</p></htmltext>
<tokenext>Comcast does not intercept port 53 .
A check using Netalyzer from ICSI or running a dig or nslookup will validate this for you against any third party resolver or any of the Comcast DNS servers.This is just plain old FUD .</tokentext>
<sentencetext>Comcast does not intercept port 53.
A check using Netalyzer from ICSI or running a dig or nslookup will validate this for you against any third party resolver or any of the Comcast DNS servers.This is just plain old FUD.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269837</id>
	<title>Not in Oregon</title>
	<author>Anonymous</author>
	<datestamp>1244577720000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I am using OpenDNS with Comcast here in Portland, OR because their DNS servers are way freaking slow. All indications seem to be that it is working correctly.</p></htmltext>
<tokenext>I am using OpenDNS with Comcast here in Portland , OR because their DNS servers are way freaking slow .
All indications seem to be that it is working correctly .</tokentext>
<sentencetext>I am using OpenDNS with Comcast here in Portland, OR because their DNS servers are way freaking slow.
All indications seem to be that it is working correctly.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270051</id>
	<title>Re:I really am hoping this is NOT a gullibility te</title>
	<author>Anonymous</author>
	<datestamp>1244578620000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I got a different result here. Not sure why yet, but just because they appear to be blocking incoming UDP 53 doesn't really bother me as we are are using our static for a mail server and VPN. It's being blocked alright but as of right now I dunno how or why. You can't always trust applets like this.</p><p>--Knoxville.hfc.comcastbusiness.net --</p><p>--UDP access to remote DNS servers (port 53) appears to pass through a firewall or proxy.<br>The applet was unable to transmit an arbitrary request on this UDP port, but was able to transmit a legitimate DNS request, suggesting that a proxy or firewall intercepted and blocked the deliberately invalid request.<br>The applet was unable to directly request a large DNS response. This suggests that a proxy or firewall is unable to handle large extended DNS requests or fragmented UDP traffic.--</p><p>We have a firewall alright, but aren't hosting any web pages so that might just be it too.</p></htmltext>
<tokenext>I got a different result here .
Not sure why yet , but just because they appear to be blocking incoming UDP 53 does n't really bother me as we are are using our static for a mail server and VPN .
It 's being blocked alright but as of right now I dunno how or why .
You ca n't always trust applets like this.--Knoxville.hfc.comcastbusiness.net ----UDP access to remote DNS servers ( port 53 ) appears to pass through a firewall or proxy.The applet was unable to transmit an arbitrary request on this UDP port , but was able to transmit a legitimate DNS request , suggesting that a proxy or firewall intercepted and blocked the deliberately invalid request.The applet was unable to directly request a large DNS response .
This suggests that a proxy or firewall is unable to handle large extended DNS requests or fragmented UDP traffic.--We have a firewall alright , but are n't hosting any web pages so that might just be it too .</tokentext>
<sentencetext>I got a different result here.
Not sure why yet, but just because they appear to be blocking incoming UDP 53 doesn't really bother me as we are are using our static for a mail server and VPN.
It's being blocked alright but as of right now I dunno how or why.
You can't always trust applets like this.--Knoxville.hfc.comcastbusiness.net ----UDP access to remote DNS servers (port 53) appears to pass through a firewall or proxy.The applet was unable to transmit an arbitrary request on this UDP port, but was able to transmit a legitimate DNS request, suggesting that a proxy or firewall intercepted and blocked the deliberately invalid request.The applet was unable to directly request a large DNS response.
This suggests that a proxy or firewall is unable to handle large extended DNS requests or fragmented UDP traffic.--We have a firewall alright, but aren't hosting any web pages so that might just be it too.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269115</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28274543</id>
	<title>Verified @Comcast in Salem, Oregon</title>
	<author>Anonymous</author>
	<datestamp>1244562540000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I can confirm DNS is redirected from Comcast IP 76.115.5.109 in Salem, Oregon using NetCat to open a port on a server I have sitting in Seattle, Washington and verifying the port responds to a dig client sitting in Kent, Washington.  The Seattle and Kent machines are not on Comcast's network.</p><p>If I allow Comcast's server to resolve my request (both existant and NXDOMAIN) the result is correct.  If I try to force use of a specific resolver, my request never makes it to the resolver and times out.</p></htmltext>
<tokenext>I can confirm DNS is redirected from Comcast IP 76.115.5.109 in Salem , Oregon using NetCat to open a port on a server I have sitting in Seattle , Washington and verifying the port responds to a dig client sitting in Kent , Washington .
The Seattle and Kent machines are not on Comcast 's network.If I allow Comcast 's server to resolve my request ( both existant and NXDOMAIN ) the result is correct .
If I try to force use of a specific resolver , my request never makes it to the resolver and times out .</tokentext>
<sentencetext>I can confirm DNS is redirected from Comcast IP 76.115.5.109 in Salem, Oregon using NetCat to open a port on a server I have sitting in Seattle, Washington and verifying the port responds to a dig client sitting in Kent, Washington.
The Seattle and Kent machines are not on Comcast's network.If I allow Comcast's server to resolve my request (both existant and NXDOMAIN) the result is correct.
If I try to force use of a specific resolver, my request never makes it to the resolver and times out.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272575</id>
	<title>Netalyzer results - Peachtree City, GA</title>
	<author>thebigbadme</author>
	<datestamp>1244547240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><a href="http://n1.netalyzr.icsi.berkeley.edu/summary/id=43ca253f-12268-d90b4111-dd9a-4663-ac6d" title="berkeley.edu" rel="nofollow">http://n1.netalyzr.icsi.berkeley.edu/summary/id=43ca253f-12268-d90b4111-dd9a-4663-ac6d</a> [berkeley.edu]</p><p>Currently in Peachtree City Georgia, Comcast triple play service - across wifi 2 stories away from base in concrete apt. structure</p></htmltext>
<tokenext>http : //n1.netalyzr.icsi.berkeley.edu/summary/id = 43ca253f-12268-d90b4111-dd9a-4663-ac6d [ berkeley.edu ] Currently in Peachtree City Georgia , Comcast triple play service - across wifi 2 stories away from base in concrete apt .
structure</tokentext>
<sentencetext>http://n1.netalyzr.icsi.berkeley.edu/summary/id=43ca253f-12268-d90b4111-dd9a-4663-ac6d [berkeley.edu]Currently in Peachtree City Georgia, Comcast triple play service - across wifi 2 stories away from base in concrete apt.
structure</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269637</id>
	<title>Re:Not happening to me</title>
	<author>EvilBudMan</author>
	<datestamp>1244576820000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p>Funny,</p><p>Here are the results from a static IP:</p><p>--Knoxville.hfc.comcastbusiness.net --</p><p>--UDP access to remote DNS servers (port 53) appears to pass through a firewall or proxy.<br>The applet was unable to transmit an arbitrary request on this UDP port, but was able to transmit a legitimate DNS request, suggesting that a proxy or firewall intercepted and blocked the deliberately invalid request.<br>The applet was unable to directly request a large DNS response. This suggests that a proxy or firewall is unable to handle large extended DNS requests or fragmented UDP traffic.--</p><p>There might be some other issues here:<br><a href="http://www.auditmypc.com/port/udp-port-53.asp" title="auditmypc.com">http://www.auditmypc.com/port/udp-port-53.asp</a> [auditmypc.com]</p></htmltext>
<tokenext>Funny,Here are the results from a static IP : --Knoxville.hfc.comcastbusiness.net ----UDP access to remote DNS servers ( port 53 ) appears to pass through a firewall or proxy.The applet was unable to transmit an arbitrary request on this UDP port , but was able to transmit a legitimate DNS request , suggesting that a proxy or firewall intercepted and blocked the deliberately invalid request.The applet was unable to directly request a large DNS response .
This suggests that a proxy or firewall is unable to handle large extended DNS requests or fragmented UDP traffic.--There might be some other issues here : http : //www.auditmypc.com/port/udp-port-53.asp [ auditmypc.com ]</tokentext>
<sentencetext>Funny,Here are the results from a static IP:--Knoxville.hfc.comcastbusiness.net ----UDP access to remote DNS servers (port 53) appears to pass through a firewall or proxy.The applet was unable to transmit an arbitrary request on this UDP port, but was able to transmit a legitimate DNS request, suggesting that a proxy or firewall intercepted and blocked the deliberately invalid request.The applet was unable to directly request a large DNS response.
This suggests that a proxy or firewall is unable to handle large extended DNS requests or fragmented UDP traffic.--There might be some other issues here:http://www.auditmypc.com/port/udp-port-53.asp [auditmypc.com]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269131</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272483</id>
	<title>Oh well eathlink's not found page is interesting..</title>
	<author>Anonymous</author>
	<datestamp>1244546760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Try browsing to <a href="http://207.69.131.9/" title="207.69.131.9">http://207.69.131.9/</a> [207.69.131.9]</p><p>I am getting...<br>"We are sorry, porn cannot be found.<br>We suggest that you check the spelling of the web address or try a different search term."</p><p>I did not search for anything.........</p></htmltext>
<tokenext>Try browsing to http : //207.69.131.9/ [ 207.69.131.9 ] I am getting... " We are sorry , porn can not be found.We suggest that you check the spelling of the web address or try a different search term .
" I did not search for anything........ .</tokentext>
<sentencetext>Try browsing to http://207.69.131.9/ [207.69.131.9]I am getting..."We are sorry, porn cannot be found.We suggest that you check the spelling of the web address or try a different search term.
"I did not search for anything.........</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269453</id>
	<title>Boston South Shore: Nope</title>
	<author>Anonymous</author>
	<datestamp>1244576100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><tt>[machine]:~ [user]$ nslookup comcast.sucks.com testserv.mydomain.com<br>;; connection timed out; no servers could be reached</tt> <p>This was tested on testserv.mydomain.com (doesn't exist) because I knew it wouldn't respond. I don't have an outside box to test it with, so while not 100\% conclusive, according to this test I should still get a DNS response if Comcast is intercepting. ICSI Netalyzr shows the following:</p><p> <tt>Basic UDP access is available.<br>Direct UDP access to remote DNS servers (port 53) is allowed.
The applet was also able to directly request a large DNS response.<br>Direct UDP access to remote MSSQL servers (port 1434) is allowed.<br>Direct TCP access to remote FTP servers (port 21) is allowed.<br>Direct TCP access to remote SSH servers (port 22) is allowed.<br>Direct TCP access to remote SMTP servers (port 25) is allowed.<br> <b>Direct TCP access to remote DNS servers (port 53) is allowed.</b> <br>Direct TCP access to remote HTTP servers (port 80) is allowed.<br>Direct TCP access to remote POP servers (port 110) is allowed.<br>Direct TCP access to remote RPC servers (port 135) is blocked. This is probably for security reasons, as this protocol is generally not designed for use outside the local network.<br>Direct TCP access to remote NetBIOS servers (port 139) is blocked. This is probably for security reasons, as this protocol is generally not designed for use outside the local network.<br>Direct TCP access to remote IMAP servers (port 143) is allowed.<br>Direct TCP access to remote SNMP servers (port 161) is allowed.<br>Direct TCP access to remote HTTPS servers (port 443) is allowed.<br>Direct TCP access to remote SMB servers (port 445) is blocked. This is probably for security reasons, as this protocol is generally not designed for use outside the local network.<br>Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.<br>Direct TCP access to remote secure IMAP servers (port 585) is allowed.<br>Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.<br>Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.<br>Direct TCP access to remote POP/SSL servers (port 995) is allowed.<br>Direct TCP access to remote SIP servers (port 5060) is allowed.<br>Direct TCP access to remote BitTorrent servers (port 6881) is allowed.</tt> </p><p>Are you sure Comcast is doing this, or is it being intercepted by a NAT gateway or proxy?</p></htmltext>
<tokenext>[ machine ] : ~ [ user ] $ nslookup comcast.sucks.com testserv.mydomain.com ; ; connection timed out ; no servers could be reached This was tested on testserv.mydomain.com ( does n't exist ) because I knew it would n't respond .
I do n't have an outside box to test it with , so while not 100 \ % conclusive , according to this test I should still get a DNS response if Comcast is intercepting .
ICSI Netalyzr shows the following : Basic UDP access is available.Direct UDP access to remote DNS servers ( port 53 ) is allowed .
The applet was also able to directly request a large DNS response.Direct UDP access to remote MSSQL servers ( port 1434 ) is allowed.Direct TCP access to remote FTP servers ( port 21 ) is allowed.Direct TCP access to remote SSH servers ( port 22 ) is allowed.Direct TCP access to remote SMTP servers ( port 25 ) is allowed .
Direct TCP access to remote DNS servers ( port 53 ) is allowed .
Direct TCP access to remote HTTP servers ( port 80 ) is allowed.Direct TCP access to remote POP servers ( port 110 ) is allowed.Direct TCP access to remote RPC servers ( port 135 ) is blocked .
This is probably for security reasons , as this protocol is generally not designed for use outside the local network.Direct TCP access to remote NetBIOS servers ( port 139 ) is blocked .
This is probably for security reasons , as this protocol is generally not designed for use outside the local network.Direct TCP access to remote IMAP servers ( port 143 ) is allowed.Direct TCP access to remote SNMP servers ( port 161 ) is allowed.Direct TCP access to remote HTTPS servers ( port 443 ) is allowed.Direct TCP access to remote SMB servers ( port 445 ) is blocked .
This is probably for security reasons , as this protocol is generally not designed for use outside the local network.Direct TCP access to remote SMTP/SSL servers ( port 465 ) is allowed.Direct TCP access to remote secure IMAP servers ( port 585 ) is allowed.Direct TCP access to remote authenticated SMTP servers ( port 587 ) is allowed.Direct TCP access to remote IMAP/SSL servers ( port 993 ) is allowed.Direct TCP access to remote POP/SSL servers ( port 995 ) is allowed.Direct TCP access to remote SIP servers ( port 5060 ) is allowed.Direct TCP access to remote BitTorrent servers ( port 6881 ) is allowed .
Are you sure Comcast is doing this , or is it being intercepted by a NAT gateway or proxy ?</tokentext>
<sentencetext>[machine]:~ [user]$ nslookup comcast.sucks.com testserv.mydomain.com;; connection timed out; no servers could be reached This was tested on testserv.mydomain.com (doesn't exist) because I knew it wouldn't respond.
I don't have an outside box to test it with, so while not 100\% conclusive, according to this test I should still get a DNS response if Comcast is intercepting.
ICSI Netalyzr shows the following: Basic UDP access is available.Direct UDP access to remote DNS servers (port 53) is allowed.
The applet was also able to directly request a large DNS response.Direct UDP access to remote MSSQL servers (port 1434) is allowed.Direct TCP access to remote FTP servers (port 21) is allowed.Direct TCP access to remote SSH servers (port 22) is allowed.Direct TCP access to remote SMTP servers (port 25) is allowed.
Direct TCP access to remote DNS servers (port 53) is allowed.
Direct TCP access to remote HTTP servers (port 80) is allowed.Direct TCP access to remote POP servers (port 110) is allowed.Direct TCP access to remote RPC servers (port 135) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.Direct TCP access to remote NetBIOS servers (port 139) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.Direct TCP access to remote IMAP servers (port 143) is allowed.Direct TCP access to remote SNMP servers (port 161) is allowed.Direct TCP access to remote HTTPS servers (port 443) is allowed.Direct TCP access to remote SMB servers (port 445) is blocked.
This is probably for security reasons, as this protocol is generally not designed for use outside the local network.Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.Direct TCP access to remote secure IMAP servers (port 585) is allowed.Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.Direct TCP access to remote POP/SSL servers (port 995) is allowed.Direct TCP access to remote SIP servers (port 5060) is allowed.Direct TCP access to remote BitTorrent servers (port 6881) is allowed.
Are you sure Comcast is doing this, or is it being intercepted by a NAT gateway or proxy?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275793</id>
	<title>Re:Official Response</title>
	<author>Anonymous</author>
	<datestamp>1244572980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Way to be a dick to a hard working front line employee... yeah, I'm sure Comcast Bonny will get right on calling the board about the issues you mention...</htmltext>
<tokenext>Way to be a dick to a hard working front line employee... yeah , I 'm sure Comcast Bonny will get right on calling the board about the issues you mention.. .</tokentext>
<sentencetext>Way to be a dick to a hard working front line employee... yeah, I'm sure Comcast Bonny will get right on calling the board about the issues you mention...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271463</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273941</id>
	<title>Previous Problems in Colorado</title>
	<author>\_Nuke\_</author>
	<datestamp>1244557020000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I haven't had time to re-test to find out what my current situation is, but I can tell you that I have experienced COMCAST mucking up my DNS traffic in the past.
<br> <br>
I have a Linux server on my local network that acts as a caching DNS for all of my client machines.  Several months ago I found that there were large holes in my internet access (including for some reason, most hotels in Las Vegas... I was planning a vacation).
<br> <br>
I have 2 separate internet connections to my house, one from COMCAST and one from QWEST.  I did not do significant detective work when I had the problem.  I used some online DNS tools to verify that the sites had good DNS entries (when not querying through COMCAST), I then accessed them with IP addresses successfully, SO, I went to my router and added a rule for all port 53 traffic to go over the QWEST connnection and (surprise)... everything worked!
<br> <br>
I chalked it up to something being messed up on COMCAST's network and not a nefarious plot; I left the rule in to direct all of the port 53 traffic out the QWEST connection and I haven't had a similar problem since.
<br> <br>
Nuke</htmltext>
<tokenext>I have n't had time to re-test to find out what my current situation is , but I can tell you that I have experienced COMCAST mucking up my DNS traffic in the past .
I have a Linux server on my local network that acts as a caching DNS for all of my client machines .
Several months ago I found that there were large holes in my internet access ( including for some reason , most hotels in Las Vegas... I was planning a vacation ) .
I have 2 separate internet connections to my house , one from COMCAST and one from QWEST .
I did not do significant detective work when I had the problem .
I used some online DNS tools to verify that the sites had good DNS entries ( when not querying through COMCAST ) , I then accessed them with IP addresses successfully , SO , I went to my router and added a rule for all port 53 traffic to go over the QWEST connnection and ( surprise ) ... everything worked !
I chalked it up to something being messed up on COMCAST 's network and not a nefarious plot ; I left the rule in to direct all of the port 53 traffic out the QWEST connection and I have n't had a similar problem since .
Nuke</tokentext>
<sentencetext>I haven't had time to re-test to find out what my current situation is, but I can tell you that I have experienced COMCAST mucking up my DNS traffic in the past.
I have a Linux server on my local network that acts as a caching DNS for all of my client machines.
Several months ago I found that there were large holes in my internet access (including for some reason, most hotels in Las Vegas... I was planning a vacation).
I have 2 separate internet connections to my house, one from COMCAST and one from QWEST.
I did not do significant detective work when I had the problem.
I used some online DNS tools to verify that the sites had good DNS entries (when not querying through COMCAST), I then accessed them with IP addresses successfully, SO, I went to my router and added a rule for all port 53 traffic to go over the QWEST connnection and (surprise)... everything worked!
I chalked it up to something being messed up on COMCAST's network and not a nefarious plot; I left the rule in to direct all of the port 53 traffic out the QWEST connection and I haven't had a similar problem since.
Nuke</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270469</id>
	<title>Re:Damn! That may stop my plan......</title>
	<author>Guanix</author>
	<datestamp>1244580180000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>Have you heard of IP over DNS? The DNStunnel software sends IP packets as TXT records over a real DNS, the client sends data in the request itself. Since these are real resolvable DNS records, proxying port 53 won't work. When I tried this software, I could only get a single stream over the tunnel, so I ran SSH over the DNStunnel and used ssh to forward a TCP port that I then ran OpenVPN on. This actually works, but it is very slow. And I can imagine that people would eventually find out because the wifi provider's DNS cache will fill up with IP data.</p></htmltext>
<tokenext>Have you heard of IP over DNS ?
The DNStunnel software sends IP packets as TXT records over a real DNS , the client sends data in the request itself .
Since these are real resolvable DNS records , proxying port 53 wo n't work .
When I tried this software , I could only get a single stream over the tunnel , so I ran SSH over the DNStunnel and used ssh to forward a TCP port that I then ran OpenVPN on .
This actually works , but it is very slow .
And I can imagine that people would eventually find out because the wifi provider 's DNS cache will fill up with IP data .</tokentext>
<sentencetext>Have you heard of IP over DNS?
The DNStunnel software sends IP packets as TXT records over a real DNS, the client sends data in the request itself.
Since these are real resolvable DNS records, proxying port 53 won't work.
When I tried this software, I could only get a single stream over the tunnel, so I ran SSH over the DNStunnel and used ssh to forward a TCP port that I then ran OpenVPN on.
This actually works, but it is very slow.
And I can imagine that people would eventually find out because the wifi provider's DNS cache will fill up with IP data.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269365</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270199</id>
	<title>ICSI Results in California</title>
	<author>Vexer77</author>
	<datestamp>1244579160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Comcast user in California using OpenDNS with following ICSI Netalyzer results:</p><p>Result Summary<br>c-24-7-17-xxx.hsd1.ca.comcast.net / 24.7.17.xxx<br>Recorded at 15:13 EDT (19:13 UTC) on Tue, June 09 2009. Permalink. Transcript. Wildcard DNS content.<br>Noteworthy Events</p><p>Major Abnormalities</p><p>
    * We received unexpected and possibly dangerous results when looking up important names</p><p>Minor Aberrations</p><p>
    * Your DNS resolver returns results even when no such server exists</p><p>Address-based Tests</p><p>NAT detection: NAT Detected</p><p>Your global IP address is 24.7.17.xxx while your local one is 192.168.1.xxx. You are behind a NAT. Your local address is in unroutable address space.</p><p>Your NAT renumbers TCP source ports sequentially. The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis.</p><p>port sequence plot</p><p>DNS-based host information: OK<br>You are not a Tor exit node for HTTP traffic.<br>You are listed on the Spamhaus Policy Based Blacklist, meaning that your provider has designated your address block as one that should not be sending any email.<br>The SORBS DUHL believes you are using a dynamically assigned IP address.<br>Reachability Tests</p><p>General connectivity: OK<br>Basic UDP access is available.<br>Direct UDP access to remote DNS servers (port 53) is allowed.<br>The applet was also able to directly request a large DNS response.<br>Direct UDP access to remote MSSQL servers (port 1434) is allowed.<br>Direct TCP access to remote FTP servers (port 21) is allowed.<br>Direct TCP access to remote SSH servers (port 22) is allowed.<br>Direct TCP access to remote SMTP servers (port 25) is allowed.<br>Direct TCP access to remote DNS servers (port 53) is allowed.<br>Direct TCP access to remote HTTP servers (port 80) is allowed.<br>Direct TCP access to remote POP servers (port 110) is allowed.<br>Direct TCP access to remote RPC servers (port 135) is blocked.<br>This is probably for security reasons, as this protocol is generally not designed for use outside the local network.<br>Direct TCP access to remote NetBIOS servers (port 139) is blocked.<br>This is probably for security reasons, as this protocol is generally not designed for use outside the local network.<br>Direct TCP access to remote IMAP servers (port 143) is allowed.<br>Direct TCP access to remote SNMP servers (port 161) is allowed.<br>Direct TCP access to remote HTTPS servers (port 443) is allowed.<br>Direct TCP access to remote SMB servers (port 445) is blocked.<br>This is probably for security reasons, as this protocol is generally not designed for use outside the local network.<br>Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.<br>Direct TCP access to remote secure IMAP servers (port 585) is allowed.<br>Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.<br>Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.<br>Direct TCP access to remote POP/SSL servers (port 995) is allowed.<br>Direct TCP access to remote SIP servers (port 5060) is allowed.<br>Direct TCP access to remote BitTorrent servers (port 6881) is allowed.<br>Network Access Link Properties</p><p>Network latency measurements: Latency: 81ms Loss: 0.0\%<br>The round-trip time (RTT) between your computer and our server is 81 msec, which is good.<br>We recorded no packet loss between your system and our server.</p><p>TCP connection setup latency: 98ms<br>The time it takes your computer to set up a TCP connection with our server is 98 msec, which is good.</p><p>Network bandwidth measurements: Upload 1.0 Mbit/sec, Download 6.5 Mbit/sec<br>Your Uplink: We measured your uplink's sending bandwidth at 1.0 Mbit/sec. This level of bandwidth works well for many users.<br>Your Downlink: We measured your downlink's receiving bandwidth at 6.5 Mbit/sec. This level of bandwidth works well for many users.</p><p>Network buffer measurements: Uplink 370 ms, Downlink 51 ms<br>We estimate your uplink as having 370</p></htmltext>
<tokenext>Comcast user in California using OpenDNS with following ICSI Netalyzer results : Result Summaryc-24-7-17-xxx.hsd1.ca.comcast.net / 24.7.17.xxxRecorded at 15 : 13 EDT ( 19 : 13 UTC ) on Tue , June 09 2009 .
Permalink. Transcript .
Wildcard DNS content.Noteworthy EventsMajor Abnormalities * We received unexpected and possibly dangerous results when looking up important namesMinor Aberrations * Your DNS resolver returns results even when no such server existsAddress-based TestsNAT detection : NAT DetectedYour global IP address is 24.7.17.xxx while your local one is 192.168.1.xxx .
You are behind a NAT .
Your local address is in unroutable address space.Your NAT renumbers TCP source ports sequentially .
The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis.port sequence plotDNS-based host information : OKYou are not a Tor exit node for HTTP traffic.You are listed on the Spamhaus Policy Based Blacklist , meaning that your provider has designated your address block as one that should not be sending any email.The SORBS DUHL believes you are using a dynamically assigned IP address.Reachability TestsGeneral connectivity : OKBasic UDP access is available.Direct UDP access to remote DNS servers ( port 53 ) is allowed.The applet was also able to directly request a large DNS response.Direct UDP access to remote MSSQL servers ( port 1434 ) is allowed.Direct TCP access to remote FTP servers ( port 21 ) is allowed.Direct TCP access to remote SSH servers ( port 22 ) is allowed.Direct TCP access to remote SMTP servers ( port 25 ) is allowed.Direct TCP access to remote DNS servers ( port 53 ) is allowed.Direct TCP access to remote HTTP servers ( port 80 ) is allowed.Direct TCP access to remote POP servers ( port 110 ) is allowed.Direct TCP access to remote RPC servers ( port 135 ) is blocked.This is probably for security reasons , as this protocol is generally not designed for use outside the local network.Direct TCP access to remote NetBIOS servers ( port 139 ) is blocked.This is probably for security reasons , as this protocol is generally not designed for use outside the local network.Direct TCP access to remote IMAP servers ( port 143 ) is allowed.Direct TCP access to remote SNMP servers ( port 161 ) is allowed.Direct TCP access to remote HTTPS servers ( port 443 ) is allowed.Direct TCP access to remote SMB servers ( port 445 ) is blocked.This is probably for security reasons , as this protocol is generally not designed for use outside the local network.Direct TCP access to remote SMTP/SSL servers ( port 465 ) is allowed.Direct TCP access to remote secure IMAP servers ( port 585 ) is allowed.Direct TCP access to remote authenticated SMTP servers ( port 587 ) is allowed.Direct TCP access to remote IMAP/SSL servers ( port 993 ) is allowed.Direct TCP access to remote POP/SSL servers ( port 995 ) is allowed.Direct TCP access to remote SIP servers ( port 5060 ) is allowed.Direct TCP access to remote BitTorrent servers ( port 6881 ) is allowed.Network Access Link PropertiesNetwork latency measurements : Latency : 81ms Loss : 0.0 \ % The round-trip time ( RTT ) between your computer and our server is 81 msec , which is good.We recorded no packet loss between your system and our server.TCP connection setup latency : 98msThe time it takes your computer to set up a TCP connection with our server is 98 msec , which is good.Network bandwidth measurements : Upload 1.0 Mbit/sec , Download 6.5 Mbit/secYour Uplink : We measured your uplink 's sending bandwidth at 1.0 Mbit/sec .
This level of bandwidth works well for many users.Your Downlink : We measured your downlink 's receiving bandwidth at 6.5 Mbit/sec .
This level of bandwidth works well for many users.Network buffer measurements : Uplink 370 ms , Downlink 51 msWe estimate your uplink as having 370</tokentext>
<sentencetext>Comcast user in California using OpenDNS with following ICSI Netalyzer results:Result Summaryc-24-7-17-xxx.hsd1.ca.comcast.net / 24.7.17.xxxRecorded at 15:13 EDT (19:13 UTC) on Tue, June 09 2009.
Permalink. Transcript.
Wildcard DNS content.Noteworthy EventsMajor Abnormalities
    * We received unexpected and possibly dangerous results when looking up important namesMinor Aberrations
    * Your DNS resolver returns results even when no such server existsAddress-based TestsNAT detection: NAT DetectedYour global IP address is 24.7.17.xxx while your local one is 192.168.1.xxx.
You are behind a NAT.
Your local address is in unroutable address space.Your NAT renumbers TCP source ports sequentially.
The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis.port sequence plotDNS-based host information: OKYou are not a Tor exit node for HTTP traffic.You are listed on the Spamhaus Policy Based Blacklist, meaning that your provider has designated your address block as one that should not be sending any email.The SORBS DUHL believes you are using a dynamically assigned IP address.Reachability TestsGeneral connectivity: OKBasic UDP access is available.Direct UDP access to remote DNS servers (port 53) is allowed.The applet was also able to directly request a large DNS response.Direct UDP access to remote MSSQL servers (port 1434) is allowed.Direct TCP access to remote FTP servers (port 21) is allowed.Direct TCP access to remote SSH servers (port 22) is allowed.Direct TCP access to remote SMTP servers (port 25) is allowed.Direct TCP access to remote DNS servers (port 53) is allowed.Direct TCP access to remote HTTP servers (port 80) is allowed.Direct TCP access to remote POP servers (port 110) is allowed.Direct TCP access to remote RPC servers (port 135) is blocked.This is probably for security reasons, as this protocol is generally not designed for use outside the local network.Direct TCP access to remote NetBIOS servers (port 139) is blocked.This is probably for security reasons, as this protocol is generally not designed for use outside the local network.Direct TCP access to remote IMAP servers (port 143) is allowed.Direct TCP access to remote SNMP servers (port 161) is allowed.Direct TCP access to remote HTTPS servers (port 443) is allowed.Direct TCP access to remote SMB servers (port 445) is blocked.This is probably for security reasons, as this protocol is generally not designed for use outside the local network.Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.Direct TCP access to remote secure IMAP servers (port 585) is allowed.Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.Direct TCP access to remote POP/SSL servers (port 995) is allowed.Direct TCP access to remote SIP servers (port 5060) is allowed.Direct TCP access to remote BitTorrent servers (port 6881) is allowed.Network Access Link PropertiesNetwork latency measurements: Latency: 81ms Loss: 0.0\%The round-trip time (RTT) between your computer and our server is 81 msec, which is good.We recorded no packet loss between your system and our server.TCP connection setup latency: 98msThe time it takes your computer to set up a TCP connection with our server is 98 msec, which is good.Network bandwidth measurements: Upload 1.0 Mbit/sec, Download 6.5 Mbit/secYour Uplink: We measured your uplink's sending bandwidth at 1.0 Mbit/sec.
This level of bandwidth works well for many users.Your Downlink: We measured your downlink's receiving bandwidth at 6.5 Mbit/sec.
This level of bandwidth works well for many users.Network buffer measurements: Uplink 370 ms, Downlink 51 msWe estimate your uplink as having 370</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270613</id>
	<title>Re:Not happening to me</title>
	<author>falconwolf</author>
	<datestamp>1244580660000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p><b><i>I'm a Comcast user, and I run a DNS server for a few private domains that only I use</i></b></p><p><i>Are you running that and hoping that your dynamic IP address doesn't change or do you have a business account with a fixed IP?</i></p><p>My access is through Comcast, though like TFA's writer I get it from Earthlink, and I have a static IP with a consumer not a business account.</p><p>

Falcon</p></htmltext>
<tokenext>I 'm a Comcast user , and I run a DNS server for a few private domains that only I useAre you running that and hoping that your dynamic IP address does n't change or do you have a business account with a fixed IP ? My access is through Comcast , though like TFA 's writer I get it from Earthlink , and I have a static IP with a consumer not a business account .
Falcon</tokentext>
<sentencetext>I'm a Comcast user, and I run a DNS server for a few private domains that only I useAre you running that and hoping that your dynamic IP address doesn't change or do you have a business account with a fixed IP?My access is through Comcast, though like TFA's writer I get it from Earthlink, and I have a static IP with a consumer not a business account.
Falcon</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269131</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275215</id>
	<title>Seems plausible in Salt Lake City</title>
	<author>iroberts</author>
	<datestamp>1244568480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I've noticed for some time that it seems whenever comcast dns is not working (and this is *very* frequent, for periods of 15 seconds to a minute, as often as not), that neither do any other dns servers.  I ran a test just now, periodically doing lookups through comcast and through 4.2.2.1, and there appeared to be a very high correlation between failures of the two.  At the same time, I was also running a ping out to google, and it never missed a beat.

This would suggest that either comcast is proxying dns traffic, or does some weird traffic shaping on port 53.</htmltext>
<tokenext>I 've noticed for some time that it seems whenever comcast dns is not working ( and this is * very * frequent , for periods of 15 seconds to a minute , as often as not ) , that neither do any other dns servers .
I ran a test just now , periodically doing lookups through comcast and through 4.2.2.1 , and there appeared to be a very high correlation between failures of the two .
At the same time , I was also running a ping out to google , and it never missed a beat .
This would suggest that either comcast is proxying dns traffic , or does some weird traffic shaping on port 53 .</tokentext>
<sentencetext>I've noticed for some time that it seems whenever comcast dns is not working (and this is *very* frequent, for periods of 15 seconds to a minute, as often as not), that neither do any other dns servers.
I ran a test just now, periodically doing lookups through comcast and through 4.2.2.1, and there appeared to be a very high correlation between failures of the two.
At the same time, I was also running a ping out to google, and it never missed a beat.
This would suggest that either comcast is proxying dns traffic, or does some weird traffic shaping on port 53.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270115</id>
	<title>Delaware seems fine</title>
	<author>wembley fraggle</author>
	<datestamp>1244578860000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>http://n7.netalyzr.icsi.berkeley.edu/summary/id=ae8199f5-24744-ed002743-edf2-4f04-8f17</p><p>from the report:<br>"Direct UDP access to remote DNS servers (port 53) is allowed.<br>The applet was also able to directly request a large DNS response."</p></htmltext>
<tokenext>http : //n7.netalyzr.icsi.berkeley.edu/summary/id = ae8199f5-24744-ed002743-edf2-4f04-8f17from the report : " Direct UDP access to remote DNS servers ( port 53 ) is allowed.The applet was also able to directly request a large DNS response .
"</tokentext>
<sentencetext>http://n7.netalyzr.icsi.berkeley.edu/summary/id=ae8199f5-24744-ed002743-edf2-4f04-8f17from the report:"Direct UDP access to remote DNS servers (port 53) is allowed.The applet was also able to directly request a large DNS response.
"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269143</id>
	<title>Comcast is not alone in this</title>
	<author>timon</author>
	<datestamp>1244575200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I use Sprint Mobile Broadband at home and the last time I checked (several months ago), they were still intercepting and redirecting port 53 traffic.</p></htmltext>
<tokenext>I use Sprint Mobile Broadband at home and the last time I checked ( several months ago ) , they were still intercepting and redirecting port 53 traffic .</tokentext>
<sentencetext>I use Sprint Mobile Broadband at home and the last time I checked (several months ago), they were still intercepting and redirecting port 53 traffic.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275077</id>
	<title>Re:Not happening to me</title>
	<author>PitaBred</author>
	<datestamp>1244567580000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I'm in Denver on Comcast, dynamic IP:<blockquote><div><p>Direct UDP access to remote DNS servers (port 53) is allowed.
The applet was also able to directly request a large DNS response.</p></div> </blockquote><p>

I think this is the <a href="http://netalyzr.icsi.berkeley.edu/restore/id=ae8199f5-26097-773635ac-bf92-4d95-8848" title="berkeley.edu">permalink</a> [berkeley.edu].</p></div>
	</htmltext>
<tokenext>I 'm in Denver on Comcast , dynamic IP : Direct UDP access to remote DNS servers ( port 53 ) is allowed .
The applet was also able to directly request a large DNS response .
I think this is the permalink [ berkeley.edu ] .</tokentext>
<sentencetext>I'm in Denver on Comcast, dynamic IP:Direct UDP access to remote DNS servers (port 53) is allowed.
The applet was also able to directly request a large DNS response.
I think this is the permalink [berkeley.edu].
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269637</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270637</id>
	<title>Re:Comcast isn't sending you to a search for porn</title>
	<author>clone53421</author>
	<datestamp>1244580840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>-1 Uninformed</p><p>Just because the server said "ZOMG P0RN!" when you asked it for "http://207.69.131.9" doesn't mean there wasn't supposed to be a more appropriate error page when you try to navigate to "http://www.nklasebvzvk.com" and the DNS server tells you to request the page from 207.69.131.9.</p><p>Servers discriminate based on the HTTP\_HOST field all the time. You can run two separate web sites on the same server (and many hosting companies do) using the HTTP\_HOST to determine which page to send... the IP address will be the same for both domains.</p></htmltext>
<tokenext>-1 UninformedJust because the server said " ZOMG P0RN !
" when you asked it for " http : //207.69.131.9 " does n't mean there was n't supposed to be a more appropriate error page when you try to navigate to " http : //www.nklasebvzvk.com " and the DNS server tells you to request the page from 207.69.131.9.Servers discriminate based on the HTTP \ _HOST field all the time .
You can run two separate web sites on the same server ( and many hosting companies do ) using the HTTP \ _HOST to determine which page to send... the IP address will be the same for both domains .</tokentext>
<sentencetext>-1 UninformedJust because the server said "ZOMG P0RN!
" when you asked it for "http://207.69.131.9" doesn't mean there wasn't supposed to be a more appropriate error page when you try to navigate to "http://www.nklasebvzvk.com" and the DNS server tells you to request the page from 207.69.131.9.Servers discriminate based on the HTTP\_HOST field all the time.
You can run two separate web sites on the same server (and many hosting companies do) using the HTTP\_HOST to determine which page to send... the IP address will be the same for both domains.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269815</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269085</id>
	<title>Using OpenDNS on Comcast</title>
	<author>Anonymous</author>
	<datestamp>1244575080000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p>no sign of any DNS hijacking in western MA.</p></htmltext>
<tokenext>no sign of any DNS hijacking in western MA .</tokentext>
<sentencetext>no sign of any DNS hijacking in western MA.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270611</id>
	<title>Re:"Official Response"</title>
	<author>Anonymous</author>
	<datestamp>1244580660000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>1</modscore>
	<htmltext><p>Dude, there was a whole Wired article about how much effort Comcast has gone through lately with trying not to suck.  Included in this article was the whole ComcastCares Twitter thing, which proved so successful that it went from one tech not wanting people to badmouth Comcast, to a team of Comcast employees deployed specifically to respond to events such as this.</p><p>For an overwhelmingly evil company, their Twitter presence is actually one of the brightest... most human... spots that Comcast has.</p></htmltext>
<tokenext>Dude , there was a whole Wired article about how much effort Comcast has gone through lately with trying not to suck .
Included in this article was the whole ComcastCares Twitter thing , which proved so successful that it went from one tech not wanting people to badmouth Comcast , to a team of Comcast employees deployed specifically to respond to events such as this.For an overwhelmingly evil company , their Twitter presence is actually one of the brightest... most human... spots that Comcast has .</tokentext>
<sentencetext>Dude, there was a whole Wired article about how much effort Comcast has gone through lately with trying not to suck.
Included in this article was the whole ComcastCares Twitter thing, which proved so successful that it went from one tech not wanting people to badmouth Comcast, to a team of Comcast employees deployed specifically to respond to events such as this.For an overwhelmingly evil company, their Twitter presence is actually one of the brightest... most human... spots that Comcast has.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270179</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269301</id>
	<title>Re:Fuck `Em All</title>
	<author>CorporateSuit</author>
	<datestamp>1244575740000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>3</modscore>
	<htmltext>From your post, I don't think you're aware that Time Warner is actually one of the presiding members of the RIAA (and the MPAA).</htmltext>
<tokenext>From your post , I do n't think you 're aware that Time Warner is actually one of the presiding members of the RIAA ( and the MPAA ) .</tokentext>
<sentencetext>From your post, I don't think you're aware that Time Warner is actually one of the presiding members of the RIAA (and the MPAA).</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269403</id>
	<title>Thanks for publishing the trick</title>
	<author>Anonymous</author>
	<datestamp>1244575920000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Now every isp in the world will know that it could<br>be useful to do that. Thanks for letting them<br>know about these tricks. This ensures that<br>DNS will be useless in few years...</p></htmltext>
<tokenext>Now every isp in the world will know that it couldbe useful to do that .
Thanks for letting themknow about these tricks .
This ensures thatDNS will be useless in few years.. .</tokentext>
<sentencetext>Now every isp in the world will know that it couldbe useful to do that.
Thanks for letting themknow about these tricks.
This ensures thatDNS will be useless in few years...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275339</id>
	<title>Re:If you want real Comcast fun...</title>
	<author>Anonymous</author>
	<datestamp>1244569560000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Having just dealt with L1 and L2 techs with another ISP, let me tell you there's no difference in competence (Actually the one guy who DID fix my problem was AFAIK a L1 tech I got on my 4thish call BEFORE being rerouted, and unlike the 'L2' tech I'd gotten the day before this guy actually had the knowledge and router access to determine there was a problem, and get ahold of someone else with privileges to fix it. Mind you it broke the next day, and then wasn't resolved for ~3 more days when the actual network technicians came back from their weekend break... WTF?)</p><p>Anyways point is big ISPs are retarded across the board, to the point of appearing collusive.</p></htmltext>
<tokenext>Having just dealt with L1 and L2 techs with another ISP , let me tell you there 's no difference in competence ( Actually the one guy who DID fix my problem was AFAIK a L1 tech I got on my 4thish call BEFORE being rerouted , and unlike the 'L2 ' tech I 'd gotten the day before this guy actually had the knowledge and router access to determine there was a problem , and get ahold of someone else with privileges to fix it .
Mind you it broke the next day , and then was n't resolved for ~ 3 more days when the actual network technicians came back from their weekend break.. .
WTF ? ) Anyways point is big ISPs are retarded across the board , to the point of appearing collusive .</tokentext>
<sentencetext>Having just dealt with L1 and L2 techs with another ISP, let me tell you there's no difference in competence (Actually the one guy who DID fix my problem was AFAIK a L1 tech I got on my 4thish call BEFORE being rerouted, and unlike the 'L2' tech I'd gotten the day before this guy actually had the knowledge and router access to determine there was a problem, and get ahold of someone else with privileges to fix it.
Mind you it broke the next day, and then wasn't resolved for ~3 more days when the actual network technicians came back from their weekend break...
WTF?)Anyways point is big ISPs are retarded across the board, to the point of appearing collusive.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269263</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269109</id>
	<title>Neither here...</title>
	<author>Nightwraith</author>
	<datestamp>1244575140000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Doesn't seem to be happening in Northwest Indiana either.</p><p>Given the poor availability of the Comcast DNS servers in this area, forcing their use seems like a very quick way to flood their customer service lines.</p></htmltext>
<tokenext>Does n't seem to be happening in Northwest Indiana either.Given the poor availability of the Comcast DNS servers in this area , forcing their use seems like a very quick way to flood their customer service lines .</tokentext>
<sentencetext>Doesn't seem to be happening in Northwest Indiana either.Given the poor availability of the Comcast DNS servers in this area, forcing their use seems like a very quick way to flood their customer service lines.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271557</id>
	<title>Re:I really am hoping this is NOT a gullibility te</title>
	<author>Dark\_Gravity</author>
	<datestamp>1244541720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p> I took out my last subnet</p></div><p>s/subnet/octet/</p></div>
	</htmltext>
<tokenext>I took out my last subnets/subnet/octet/</tokentext>
<sentencetext> I took out my last subnets/subnet/octet/
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269115</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269427</id>
	<title>Not in philly</title>
	<author>dtdmrr</author>
	<datestamp>1244575980000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>So far</htmltext>
<tokenext>So far</tokentext>
<sentencetext>So far</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271987</id>
	<title>Per TFA It's Earthlink's Name Servers</title>
	<author>Anonymous</author>
	<datestamp>1244543760000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>From TFA:</p><p>"(Full disclosure: I don't know if it's Comcast or Earthlink that's responsible for this behavior, but Comcast is who I pay for internet access, so I'm blaming them for now, even though it's obvious Earthlink is involved)."</p><p>Later in article:</p><p>"The astute reader will notice that the addresses returned are those of the Earthlink host-not-found advertising page."</p><p>Sounds like it's Earthlink doing this (atleast, from a technical standpoint.  At OSI layer 8 = business/political layer, it could be an agreement between the two of them).  I understand why there might be some bad feeling against Comcast based on previous episodes, but based on your description it sounds like Comcast is just providing the last mile of connectivity and the actual IP communication with the Internet is Earthlink's piece (since they're your ISP).  Comcast is just handling billing (and last mile cabling / layer 2 linkage).  Taking it up with Comcast might still be useful in resolving the issue, but it sounds like they'd be the middlemen in this scenario.</p></htmltext>
<tokenext>From TFA : " ( Full disclosure : I do n't know if it 's Comcast or Earthlink that 's responsible for this behavior , but Comcast is who I pay for internet access , so I 'm blaming them for now , even though it 's obvious Earthlink is involved ) .
" Later in article : " The astute reader will notice that the addresses returned are those of the Earthlink host-not-found advertising page .
" Sounds like it 's Earthlink doing this ( atleast , from a technical standpoint .
At OSI layer 8 = business/political layer , it could be an agreement between the two of them ) .
I understand why there might be some bad feeling against Comcast based on previous episodes , but based on your description it sounds like Comcast is just providing the last mile of connectivity and the actual IP communication with the Internet is Earthlink 's piece ( since they 're your ISP ) .
Comcast is just handling billing ( and last mile cabling / layer 2 linkage ) .
Taking it up with Comcast might still be useful in resolving the issue , but it sounds like they 'd be the middlemen in this scenario .</tokentext>
<sentencetext>From TFA:"(Full disclosure: I don't know if it's Comcast or Earthlink that's responsible for this behavior, but Comcast is who I pay for internet access, so I'm blaming them for now, even though it's obvious Earthlink is involved).
"Later in article:"The astute reader will notice that the addresses returned are those of the Earthlink host-not-found advertising page.
"Sounds like it's Earthlink doing this (atleast, from a technical standpoint.
At OSI layer 8 = business/political layer, it could be an agreement between the two of them).
I understand why there might be some bad feeling against Comcast based on previous episodes, but based on your description it sounds like Comcast is just providing the last mile of connectivity and the actual IP communication with the Internet is Earthlink's piece (since they're your ISP).
Comcast is just handling billing (and last mile cabling / layer 2 linkage).
Taking it up with Comcast might still be useful in resolving the issue, but it sounds like they'd be the middlemen in this scenario.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271737</id>
	<title>Used to have a problem...</title>
	<author>Anonymous</author>
	<datestamp>1244542680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I've been a Comcast residential high-speed customer since it came out here in 2001. Between 2003 and 2005, their DNS servers would fail all the time, so I went into the router and changed the DNS servers to the "for off-campus use" DNS servers of my local university. Worked like a charm.</p><p>The problem is since long gone. I might get blasted for saying this, but I've actually had really good luck with Comcast high-speed Internet.</p><p>The only part that sucks? Back in 2001 when it was Excite@home, there was no speed cap sent to the modem, and 7 mbps was commonplace. Today, my modem is capped at 6.6 mbps, and I typically get around 5 in a speed test.</p></htmltext>
<tokenext>I 've been a Comcast residential high-speed customer since it came out here in 2001 .
Between 2003 and 2005 , their DNS servers would fail all the time , so I went into the router and changed the DNS servers to the " for off-campus use " DNS servers of my local university .
Worked like a charm.The problem is since long gone .
I might get blasted for saying this , but I 've actually had really good luck with Comcast high-speed Internet.The only part that sucks ?
Back in 2001 when it was Excite @ home , there was no speed cap sent to the modem , and 7 mbps was commonplace .
Today , my modem is capped at 6.6 mbps , and I typically get around 5 in a speed test .</tokentext>
<sentencetext>I've been a Comcast residential high-speed customer since it came out here in 2001.
Between 2003 and 2005, their DNS servers would fail all the time, so I went into the router and changed the DNS servers to the "for off-campus use" DNS servers of my local university.
Worked like a charm.The problem is since long gone.
I might get blasted for saying this, but I've actually had really good luck with Comcast high-speed Internet.The only part that sucks?
Back in 2001 when it was Excite@home, there was no speed cap sent to the modem, and 7 mbps was commonplace.
Today, my modem is capped at 6.6 mbps, and I typically get around 5 in a speed test.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269269</id>
	<title>Comcast results in Houston, TX</title>
	<author>Anonymous</author>
	<datestamp>1244575620000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><p> <a href="http://n4.netalyzr.icsi.berkeley.edu/summary/id=ae819c33-16989-8a0720c9-66fb-4151-8631" title="berkeley.edu">Here are the ICSI results</a> [berkeley.edu]. Results are from a PC behind a bog-standard Linksys WRT-54g, for what it's worth.</p><p>Not my field, but I see <b>Direct TCP access to remote DNS servers (port 53) is allowed.</b> I'll leave it to the networking experts to pick through the rest of the report.</p></htmltext>
<tokenext>Here are the ICSI results [ berkeley.edu ] .
Results are from a PC behind a bog-standard Linksys WRT-54g , for what it 's worth.Not my field , but I see Direct TCP access to remote DNS servers ( port 53 ) is allowed .
I 'll leave it to the networking experts to pick through the rest of the report .</tokentext>
<sentencetext> Here are the ICSI results [berkeley.edu].
Results are from a PC behind a bog-standard Linksys WRT-54g, for what it's worth.Not my field, but I see Direct TCP access to remote DNS servers (port 53) is allowed.
I'll leave it to the networking experts to pick through the rest of the report.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269829</id>
	<title>Test market?</title>
	<author>irving47</author>
	<datestamp>1244577660000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>3</modscore>
	<htmltext><p>I don't see anyone else mentioning this,  but it seems they could be using a particular area to test this "policy"</p></htmltext>
<tokenext>I do n't see anyone else mentioning this , but it seems they could be using a particular area to test this " policy "</tokentext>
<sentencetext>I don't see anyone else mentioning this,  but it seems they could be using a particular area to test this "policy"</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272889</id>
	<title>Hmmmm</title>
	<author>DaMattster</author>
	<datestamp>1244549160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Comcast has always been a dog that likes to test the fences and then gets slapped down.  Remember their infamous "filter" that was forcibly shut down?  They want to see what they can get away with.  They'll fight and growl but if enough people notice and threaten to complain to the FCC or some other government agency, they'll stop.</htmltext>
<tokenext>Comcast has always been a dog that likes to test the fences and then gets slapped down .
Remember their infamous " filter " that was forcibly shut down ?
They want to see what they can get away with .
They 'll fight and growl but if enough people notice and threaten to complain to the FCC or some other government agency , they 'll stop .</tokentext>
<sentencetext>Comcast has always been a dog that likes to test the fences and then gets slapped down.
Remember their infamous "filter" that was forcibly shut down?
They want to see what they can get away with.
They'll fight and growl but if enough people notice and threaten to complain to the FCC or some other government agency, they'll stop.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271463</id>
	<title>Re:Official Response</title>
	<author>Linux\_ho</author>
	<datestamp>1244541300000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext>Even assuming you're a real Comcast representative, why should we believe anything any Comcast rep says, after witnessing the series of lies, stonewalling, and misdirection Comcast produced after being accused of interfering with BitTorrent traffic, and then again after being caught red-handed interfering with BitTorrent traffic?</htmltext>
<tokenext>Even assuming you 're a real Comcast representative , why should we believe anything any Comcast rep says , after witnessing the series of lies , stonewalling , and misdirection Comcast produced after being accused of interfering with BitTorrent traffic , and then again after being caught red-handed interfering with BitTorrent traffic ?</tokentext>
<sentencetext>Even assuming you're a real Comcast representative, why should we believe anything any Comcast rep says, after witnessing the series of lies, stonewalling, and misdirection Comcast produced after being accused of interfering with BitTorrent traffic, and then again after being caught red-handed interfering with BitTorrent traffic?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269531</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271371</id>
	<title>Re:Not happening to me</title>
	<author>x4r</author>
	<datestamp>1244540880000</datestamp>
	<modclass>Offtopic</modclass>
	<modscore>0</modscore>
	<htmltext>you right, and US laws was wrong. in you dream.</htmltext>
<tokenext>you right , and US laws was wrong .
in you dream .</tokentext>
<sentencetext>you right, and US laws was wrong.
in you dream.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269097</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269359</id>
	<title>Just run BIND in your computer</title>
	<author>Anonymous</author>
	<datestamp>1244575860000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>0</modscore>
	<htmltext><p>or set up a server in your LAN.. run BIND, setup to do recursive lookup...<br>use that as your DNS server</p></htmltext>
<tokenext>or set up a server in your LAN.. run BIND , setup to do recursive lookup...use that as your DNS server</tokentext>
<sentencetext>or set up a server in your LAN.. run BIND, setup to do recursive lookup...use that as your DNS server</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270323</id>
	<title>Earthlink not Comcast</title>
	<author>Anonymous</author>
	<datestamp>1244579580000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>This seems like it's an Earthlink issue not a Comcast one if it exists at all. According to the blog he's in some sort of deal with Comcast + Earthlink service. He's getting Earthlink Adverts on non-existent pages. His DNS 'reroutes' are rerouting to an Earthlink page. If there's any truth to this it's because of Earthlink + Comcast and not Comcast on its own.</p></htmltext>
<tokenext>This seems like it 's an Earthlink issue not a Comcast one if it exists at all .
According to the blog he 's in some sort of deal with Comcast + Earthlink service .
He 's getting Earthlink Adverts on non-existent pages .
His DNS 'reroutes ' are rerouting to an Earthlink page .
If there 's any truth to this it 's because of Earthlink + Comcast and not Comcast on its own .</tokentext>
<sentencetext>This seems like it's an Earthlink issue not a Comcast one if it exists at all.
According to the blog he's in some sort of deal with Comcast + Earthlink service.
He's getting Earthlink Adverts on non-existent pages.
His DNS 'reroutes' are rerouting to an Earthlink page.
If there's any truth to this it's because of Earthlink + Comcast and not Comcast on its own.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271823</id>
	<title>Unable to Confirm</title>
	<author>CyberLife</author>
	<datestamp>1244543100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Tried it from northwestern Washington-state to California. No problems.</p></htmltext>
<tokenext>Tried it from northwestern Washington-state to California .
No problems .</tokentext>
<sentencetext>Tried it from northwestern Washington-state to California.
No problems.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269435</id>
	<title>Is this happening for ANYONE?</title>
	<author>Anonymous</author>
	<datestamp>1244576040000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>5</modscore>
	<htmltext>Was the original poster a shill for some other ISP or what? An anonymous user submits a story decrying a great technical wrong by Comcast, that no one appears to be able to reproduce. So a little fact check action might in order here. Up next, "toyotasuxors@ford.com says: <i>Toyota tracking all US drivers with a device hidden in the glove box!</i></htmltext>
<tokenext>Was the original poster a shill for some other ISP or what ?
An anonymous user submits a story decrying a great technical wrong by Comcast , that no one appears to be able to reproduce .
So a little fact check action might in order here .
Up next , " toyotasuxors @ ford.com says : Toyota tracking all US drivers with a device hidden in the glove box !</tokentext>
<sentencetext>Was the original poster a shill for some other ISP or what?
An anonymous user submits a story decrying a great technical wrong by Comcast, that no one appears to be able to reproduce.
So a little fact check action might in order here.
Up next, "toyotasuxors@ford.com says: Toyota tracking all US drivers with a device hidden in the glove box!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270347</id>
	<title>Not blocking in NY</title>
	<author>grimace123\_99</author>
	<datestamp>1244579640000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>Comcast DNS is working as expected in Upstate NY, I use OpenDNS from home (comcast cable service) and all is working as expected I can review my open dns logs and see that it is indeed serving me dns.</htmltext>
<tokenext>Comcast DNS is working as expected in Upstate NY , I use OpenDNS from home ( comcast cable service ) and all is working as expected I can review my open dns logs and see that it is indeed serving me dns .</tokentext>
<sentencetext>Comcast DNS is working as expected in Upstate NY, I use OpenDNS from home (comcast cable service) and all is working as expected I can review my open dns logs and see that it is indeed serving me dns.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275593</id>
	<title>Perma</title>
	<author>SchizoStatic</author>
	<datestamp>1244571300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Comcast Residential in Minnesota. I use OpenDNS to filter the net here at home so the kiddies don't hit to much porn while trying to do homework.

<a href="http://netalyzr.icsi.berkeley.edu/restore/id=482c3e43-1843-a5565296-caaa-42bf-819d" title="berkeley.edu" rel="nofollow">http://netalyzr.icsi.berkeley.edu/restore/id=482c3e43-1843-a5565296-caaa-42bf-819d</a> [berkeley.edu]</htmltext>
<tokenext>Comcast Residential in Minnesota .
I use OpenDNS to filter the net here at home so the kiddies do n't hit to much porn while trying to do homework .
http : //netalyzr.icsi.berkeley.edu/restore/id = 482c3e43-1843-a5565296-caaa-42bf-819d [ berkeley.edu ]</tokentext>
<sentencetext>Comcast Residential in Minnesota.
I use OpenDNS to filter the net here at home so the kiddies don't hit to much porn while trying to do homework.
http://netalyzr.icsi.berkeley.edu/restore/id=482c3e43-1843-a5565296-caaa-42bf-819d [berkeley.edu]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273869</id>
	<title>EARTHLINK!!!!!!!</title>
	<author>Tokerat</author>
	<datestamp>1244556480000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Everyone that has reported this problem has a Comcast account that is somehow lined with Earthlink service. Even the linked article says so. Why don't we investigate that route? Did Comcast buy out Earthlink recently? Is there some kind of cross-promotional service where you buy from Earthlink over Comcast infrastructure? They fit into this somehow...</p></htmltext>
<tokenext>Everyone that has reported this problem has a Comcast account that is somehow lined with Earthlink service .
Even the linked article says so .
Why do n't we investigate that route ?
Did Comcast buy out Earthlink recently ?
Is there some kind of cross-promotional service where you buy from Earthlink over Comcast infrastructure ?
They fit into this somehow.. .</tokentext>
<sentencetext>Everyone that has reported this problem has a Comcast account that is somehow lined with Earthlink service.
Even the linked article says so.
Why don't we investigate that route?
Did Comcast buy out Earthlink recently?
Is there some kind of cross-promotional service where you buy from Earthlink over Comcast infrastructure?
They fit into this somehow...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270481</id>
	<title>Ob. Comic</title>
	<author>DarthVain</author>
	<datestamp>1244580180000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Sounds like more of the same...</p><p><a href="http://www.gucomics.com/comic/?cdate=20090527" title="gucomics.com">http://www.gucomics.com/comic/?cdate=20090527</a> [gucomics.com]</p></htmltext>
<tokenext>Sounds like more of the same...http : //www.gucomics.com/comic/ ? cdate = 20090527 [ gucomics.com ]</tokentext>
<sentencetext>Sounds like more of the same...http://www.gucomics.com/comic/?cdate=20090527 [gucomics.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275113</id>
	<title>No problem in Boston</title>
	<author>Anonymous</author>
	<datestamp>1244567880000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>In the Boston, MA area, I get these results from home (dynamic IP account plugged into a NAT switch):</p><p>&gt; Direct UDP access to remote DNS servers (port 53) is allowed.<br>&gt; Direct TCP access to remote DNS servers (port 53) is allowed.</p></htmltext>
<tokenext>In the Boston , MA area , I get these results from home ( dynamic IP account plugged into a NAT switch ) : &gt; Direct UDP access to remote DNS servers ( port 53 ) is allowed. &gt; Direct TCP access to remote DNS servers ( port 53 ) is allowed .</tokentext>
<sentencetext>In the Boston, MA area, I get these results from home (dynamic IP account plugged into a NAT switch):&gt; Direct UDP access to remote DNS servers (port 53) is allowed.&gt; Direct TCP access to remote DNS servers (port 53) is allowed.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269891</id>
	<title>works fine here</title>
	<author>hymie!</author>
	<datestamp>1244577960000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Howard County, MD.  No problems using a specified DNS server.</p></htmltext>
<tokenext>Howard County , MD .
No problems using a specified DNS server .</tokentext>
<sentencetext>Howard County, MD.
No problems using a specified DNS server.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270357</id>
	<title>Re:Not happening to me</title>
	<author>Anonymous</author>
	<datestamp>1244579700000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>i hosted my own personal domain, mostly for my own benefit, on a comcast home account. I ran it for three years and only ever rarely (usually during a power outage) lost my address. I kept my ttl's relatively short... 24 hours or so, so that on the rare occasion I could fix everything easily enough...</p><p>i even ran a mail server, well configured, and was never bothered; I knew people who had poorly configured mail servers who were contacted and threatened with having their service shut off because they were running an open relay in just weeks; I don't know if it is true anymore, but it certainly seemed at the time that if you took the time to do it right, they would leave you alone...</p><p>I did have to send mail through their servers (or something... it was over 4 years ago, so details are fuzzy) as there was some smtp funkiness going on, but nothing crazy...</p></htmltext>
<tokenext>i hosted my own personal domain , mostly for my own benefit , on a comcast home account .
I ran it for three years and only ever rarely ( usually during a power outage ) lost my address .
I kept my ttl 's relatively short... 24 hours or so , so that on the rare occasion I could fix everything easily enough...i even ran a mail server , well configured , and was never bothered ; I knew people who had poorly configured mail servers who were contacted and threatened with having their service shut off because they were running an open relay in just weeks ; I do n't know if it is true anymore , but it certainly seemed at the time that if you took the time to do it right , they would leave you alone...I did have to send mail through their servers ( or something... it was over 4 years ago , so details are fuzzy ) as there was some smtp funkiness going on , but nothing crazy.. .</tokentext>
<sentencetext>i hosted my own personal domain, mostly for my own benefit, on a comcast home account.
I ran it for three years and only ever rarely (usually during a power outage) lost my address.
I kept my ttl's relatively short... 24 hours or so, so that on the rare occasion I could fix everything easily enough...i even ran a mail server, well configured, and was never bothered; I knew people who had poorly configured mail servers who were contacted and threatened with having their service shut off because they were running an open relay in just weeks; I don't know if it is true anymore, but it certainly seemed at the time that if you took the time to do it right, they would leave you alone...I did have to send mail through their servers (or something... it was over 4 years ago, so details are fuzzy) as there was some smtp funkiness going on, but nothing crazy...</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269131</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270995</id>
	<title>Re:Security</title>
	<author>Crudely\_Indecent</author>
	<datestamp>1244539260000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>That is the exact reason I redirect DNS traffic on my network.</p><p>Users cannot be trusted to enter correct information, they cannot be trusted to keep their machines free of infection and as a result, I receive more support requests.  It only took 3 escalated calls to make up my mind about DNS redirection.</p><p>No more hijacking, users on my network may utilize external DNS only if they can tunnel to it (this takes care of my business clients)</p><p>I've had no complaints (I'm serious, not a single one)</p></htmltext>
<tokenext>That is the exact reason I redirect DNS traffic on my network.Users can not be trusted to enter correct information , they can not be trusted to keep their machines free of infection and as a result , I receive more support requests .
It only took 3 escalated calls to make up my mind about DNS redirection.No more hijacking , users on my network may utilize external DNS only if they can tunnel to it ( this takes care of my business clients ) I 've had no complaints ( I 'm serious , not a single one )</tokentext>
<sentencetext>That is the exact reason I redirect DNS traffic on my network.Users cannot be trusted to enter correct information, they cannot be trusted to keep their machines free of infection and as a result, I receive more support requests.
It only took 3 escalated calls to make up my mind about DNS redirection.No more hijacking, users on my network may utilize external DNS only if they can tunnel to it (this takes care of my business clients)I've had no complaints (I'm serious, not a single one)</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269147</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28274037</id>
	<title>Re:So let me see if I have this straight...</title>
	<author>Anonymous</author>
	<datestamp>1244557860000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>I'd rather a user submit this and make a legitimate mistake versus Comcast screwing loads of customers over, which they have done in the past.  Hell, they've flat out phrackin lied in the past.</p><p>At the very least, Comcast will see the shitstorm, and be less likely to implement such a strategy if they aren't now.  It's also at least interesting to those of us who follow Comcast's screwups--their networks are not all the same or treated equally; particularly, California and western state subscribers seem to have a different network setup than the southern states, and the eastern states still a different setup.  An area which does not show this issues does not mean it's not affecting a different area.</p><p>This is the company that has unsecured URLs in user accounts.  This is a company that has TV, signal, and network monitors, yet doesn't know when entire networks go down, or argues with users or wastes people's time sending out techs versus checking main trunk lines.  This is the company that is frequently a local monopoly.</p><p>So a user made a mistake.  Darn.  Lots of people looked into it.  Good.  Comcast burned the bridge of good will from their customers a couple of years back.  They have to earn it back; it's not given.</p></htmltext>
<tokenext>I 'd rather a user submit this and make a legitimate mistake versus Comcast screwing loads of customers over , which they have done in the past .
Hell , they 've flat out phrackin lied in the past.At the very least , Comcast will see the shitstorm , and be less likely to implement such a strategy if they are n't now .
It 's also at least interesting to those of us who follow Comcast 's screwups--their networks are not all the same or treated equally ; particularly , California and western state subscribers seem to have a different network setup than the southern states , and the eastern states still a different setup .
An area which does not show this issues does not mean it 's not affecting a different area.This is the company that has unsecured URLs in user accounts .
This is a company that has TV , signal , and network monitors , yet does n't know when entire networks go down , or argues with users or wastes people 's time sending out techs versus checking main trunk lines .
This is the company that is frequently a local monopoly.So a user made a mistake .
Darn. Lots of people looked into it .
Good. Comcast burned the bridge of good will from their customers a couple of years back .
They have to earn it back ; it 's not given .</tokentext>
<sentencetext>I'd rather a user submit this and make a legitimate mistake versus Comcast screwing loads of customers over, which they have done in the past.
Hell, they've flat out phrackin lied in the past.At the very least, Comcast will see the shitstorm, and be less likely to implement such a strategy if they aren't now.
It's also at least interesting to those of us who follow Comcast's screwups--their networks are not all the same or treated equally; particularly, California and western state subscribers seem to have a different network setup than the southern states, and the eastern states still a different setup.
An area which does not show this issues does not mean it's not affecting a different area.This is the company that has unsecured URLs in user accounts.
This is a company that has TV, signal, and network monitors, yet doesn't know when entire networks go down, or argues with users or wastes people's time sending out techs versus checking main trunk lines.
This is the company that is frequently a local monopoly.So a user made a mistake.
Darn.  Lots of people looked into it.
Good.  Comcast burned the bridge of good will from their customers a couple of years back.
They have to earn it back; it's not given.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269573</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270253</id>
	<title>No problems here</title>
	<author>davmoo</author>
	<datestamp>1244579280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I use Comcast and OpenDNS.  Everything is as it should be here (central Indiana).</p></htmltext>
<tokenext>I use Comcast and OpenDNS .
Everything is as it should be here ( central Indiana ) .</tokentext>
<sentencetext>I use Comcast and OpenDNS.
Everything is as it should be here (central Indiana).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270581</id>
	<title>Not the case for me</title>
	<author>Chris Daniel</author>
	<datestamp>1244580540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I'm in the Portland, Oregon area. Tag: kdawsonfud.</htmltext>
<tokenext>I 'm in the Portland , Oregon area .
Tag : kdawsonfud .</tokentext>
<sentencetext>I'm in the Portland, Oregon area.
Tag: kdawsonfud.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28274023</id>
	<title>Re:Not happening to me</title>
	<author>clint999</author>
	<datestamp>1244557800000</datestamp>
	<modclass>None</modclass>
	<modscore>-1</modscore>
	<htmltext><blockquote><div><p>Assuming you have control of a decent firewall on both ends you can just reroute all your outbound traffic on port 53 to something of your choosing (lets say 16053) and then reroute the inbound traffic from 16053 to 53.</p></div></blockquote></div>
	</htmltext>
<tokenext>Assuming you have control of a decent firewall on both ends you can just reroute all your outbound traffic on port 53 to something of your choosing ( lets say 16053 ) and then reroute the inbound traffic from 16053 to 53 .</tokentext>
<sentencetext>Assuming you have control of a decent firewall on both ends you can just reroute all your outbound traffic on port 53 to something of your choosing (lets say 16053) and then reroute the inbound traffic from 16053 to 53.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28276945</id>
	<title>free inet</title>
	<author>Anonymous</author>
	<datestamp>1244628840000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>buy modem. plug it in. do not register the modem with comcast. change your dns manually. free inet</p></htmltext>
<tokenext>buy modem .
plug it in .
do not register the modem with comcast .
change your dns manually .
free inet</tokentext>
<sentencetext>buy modem.
plug it in.
do not register the modem with comcast.
change your dns manually.
free inet</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269307</id>
	<title>Not for me...</title>
	<author>catseye</author>
	<datestamp>1244575740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Comcast customer in Colorado, just outside of Boulder. Not happening here; I use OpenDNS and am definitely hitting their servers.</p></htmltext>
<tokenext>Comcast customer in Colorado , just outside of Boulder .
Not happening here ; I use OpenDNS and am definitely hitting their servers .</tokentext>
<sentencetext>Comcast customer in Colorado, just outside of Boulder.
Not happening here; I use OpenDNS and am definitely hitting their servers.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269925</id>
	<title>Rogers Cable in Canada does this.</title>
	<author>Anonymous</author>
	<datestamp>1244578140000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Rogers Cable in Canada does this.</p><p>It's very annoying.</p></htmltext>
<tokenext>Rogers Cable in Canada does this.It 's very annoying .</tokentext>
<sentencetext>Rogers Cable in Canada does this.It's very annoying.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28274225</id>
	<title>To thwart IP-over-DNS...</title>
	<author>PhotoGuy</author>
	<datestamp>1244559840000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Is there any chance that this is done to thwart 'IP-over-DNS' attempts?</p><p>Many ISP's will forward port 53 traffic happily, even before a cable modem is provisioned.  If you attempt to go to any site (port 80, etc.) it will redirect you to their provisioning page.  But DNS requests work.</p><p>So there are tools to funnel *all* of your traffic through a tunnel on port 53, as fake DNS requests.</p><p>You need a DNS server on the other end as an exit for the gateway, and control over your domain to redirect the requests appropriately, but I've used it on unprovisioned modems in a pinch, and it does work.  I wouldn't want to download Redhat ISO's over it, but for casual browsing when nothing else is available, it does work.  (Not recommending the practice of course.)</p><p>I could see grabbing control of port 53 to avoid this tunneling (although it's doubtful it's widespread enough to warrant such work).</p><p>In general, I'm a bit mixed on the topic; I'm all for net neutrality, but to provide a good, consistent user experience, an ISP taking control of DNS requests (and cacheing) isn't too far out there.  If they are redirecting things inappropriately, however, then that's an absolute no-no, and should be slapped down immediately...</p></htmltext>
<tokenext>Is there any chance that this is done to thwart 'IP-over-DNS ' attempts ? Many ISP 's will forward port 53 traffic happily , even before a cable modem is provisioned .
If you attempt to go to any site ( port 80 , etc .
) it will redirect you to their provisioning page .
But DNS requests work.So there are tools to funnel * all * of your traffic through a tunnel on port 53 , as fake DNS requests.You need a DNS server on the other end as an exit for the gateway , and control over your domain to redirect the requests appropriately , but I 've used it on unprovisioned modems in a pinch , and it does work .
I would n't want to download Redhat ISO 's over it , but for casual browsing when nothing else is available , it does work .
( Not recommending the practice of course .
) I could see grabbing control of port 53 to avoid this tunneling ( although it 's doubtful it 's widespread enough to warrant such work ) .In general , I 'm a bit mixed on the topic ; I 'm all for net neutrality , but to provide a good , consistent user experience , an ISP taking control of DNS requests ( and cacheing ) is n't too far out there .
If they are redirecting things inappropriately , however , then that 's an absolute no-no , and should be slapped down immediately.. .</tokentext>
<sentencetext>Is there any chance that this is done to thwart 'IP-over-DNS' attempts?Many ISP's will forward port 53 traffic happily, even before a cable modem is provisioned.
If you attempt to go to any site (port 80, etc.
) it will redirect you to their provisioning page.
But DNS requests work.So there are tools to funnel *all* of your traffic through a tunnel on port 53, as fake DNS requests.You need a DNS server on the other end as an exit for the gateway, and control over your domain to redirect the requests appropriately, but I've used it on unprovisioned modems in a pinch, and it does work.
I wouldn't want to download Redhat ISO's over it, but for casual browsing when nothing else is available, it does work.
(Not recommending the practice of course.
)I could see grabbing control of port 53 to avoid this tunneling (although it's doubtful it's widespread enough to warrant such work).In general, I'm a bit mixed on the topic; I'm all for net neutrality, but to provide a good, consistent user experience, an ISP taking control of DNS requests (and cacheing) isn't too far out there.
If they are redirecting things inappropriately, however, then that's an absolute no-no, and should be slapped down immediately...</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270511</id>
	<title>Re:Perhaps Comcast DNS proxy redirects non-respond</title>
	<author>clone53421</author>
	<datestamp>1244580240000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>they can certainly redirect to their own DNS resolvers if the specified DNS resolver is non-responsive</p></div><p>The responder wasn't non-existent, the responder was simply non-responsive. The active listen on port 53 should have caught any attempt by Comcast to see if it was a "real" DNS server. To do what you describe, they still would have had to send something to the specified DNS server, which apparently never happened.</p></div>
	</htmltext>
<tokenext>they can certainly redirect to their own DNS resolvers if the specified DNS resolver is non-responsiveThe responder was n't non-existent , the responder was simply non-responsive .
The active listen on port 53 should have caught any attempt by Comcast to see if it was a " real " DNS server .
To do what you describe , they still would have had to send something to the specified DNS server , which apparently never happened .</tokentext>
<sentencetext>they can certainly redirect to their own DNS resolvers if the specified DNS resolver is non-responsiveThe responder wasn't non-existent, the responder was simply non-responsive.
The active listen on port 53 should have caught any attempt by Comcast to see if it was a "real" DNS server.
To do what you describe, they still would have had to send something to the specified DNS server, which apparently never happened.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269809</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270683</id>
	<title>Re:Is this happening for ANYONE?</title>
	<author>Anonymous</author>
	<datestamp>1244581020000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>"toyotasuxors@ford.com says: Toyota tracking all US drivers with a device hidden in the glove box!"</p><p>You mean GM and OnStar?</p></htmltext>
<tokenext>" toyotasuxors @ ford.com says : Toyota tracking all US drivers with a device hidden in the glove box !
" You mean GM and OnStar ?</tokentext>
<sentencetext>"toyotasuxors@ford.com says: Toyota tracking all US drivers with a device hidden in the glove box!
"You mean GM and OnStar?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269435</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269633</id>
	<title>Port 53 Rerouted in Seattle :|</title>
	<author>stacysmomsmokesabong</author>
	<datestamp>1244576760000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext>I can verify this is happening in Lynnwood, WA - just north of Seattle - on my Comcast residential connection. First port 25 is blocked, now 53 is being rerouted? GD Comcast is a bunch of toolsheds.<br>
<br>
My working third party server connected to the dummy DNS server just fine, while my home Comcast connected PCs couldn't. Tested in Windows 2008, Gentoo and Windows XP @ home - same results on all 3.<br>
<br>
Webalyzer results: <a href="http://n12.netalyzr.icsi.berkeley.edu/summary/id=ae8186a4-19933-b1cad9f6-8c34-416a-ac19" title="berkeley.edu" rel="nofollow">here</a> [berkeley.edu]</htmltext>
<tokenext>I can verify this is happening in Lynnwood , WA - just north of Seattle - on my Comcast residential connection .
First port 25 is blocked , now 53 is being rerouted ?
GD Comcast is a bunch of toolsheds .
My working third party server connected to the dummy DNS server just fine , while my home Comcast connected PCs could n't .
Tested in Windows 2008 , Gentoo and Windows XP @ home - same results on all 3 .
Webalyzer results : here [ berkeley.edu ]</tokentext>
<sentencetext>I can verify this is happening in Lynnwood, WA - just north of Seattle - on my Comcast residential connection.
First port 25 is blocked, now 53 is being rerouted?
GD Comcast is a bunch of toolsheds.
My working third party server connected to the dummy DNS server just fine, while my home Comcast connected PCs couldn't.
Tested in Windows 2008, Gentoo and Windows XP @ home - same results on all 3.
Webalyzer results: here [berkeley.edu]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269949</id>
	<title>Re:Fuck `Em All</title>
	<author>element-o.p.</author>
	<datestamp>1244578200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>&quot;Froo-its of the dev-il&quot; evil?</htmltext>
<tokenext>" Froo-its of the dev-il " evil ?</tokentext>
<sentencetext>"Froo-its of the dev-il" evil?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270921</id>
	<title>Re:Official Response</title>
	<author>Anonymous</author>
	<datestamp>1244538960000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Nuff said? Really, as if thats all thats needed from a comcast flak is a flat denial with no explanation as to why some users are having problems. You sure you're cleared to know what the company is actually doing? You sure every tech knows what management is doing? Cause I don't think so. And btw I post AC because I don't care to get an account.</p></htmltext>
<tokenext>Nuff said ?
Really , as if thats all thats needed from a comcast flak is a flat denial with no explanation as to why some users are having problems .
You sure you 're cleared to know what the company is actually doing ?
You sure every tech knows what management is doing ?
Cause I do n't think so .
And btw I post AC because I do n't care to get an account .</tokentext>
<sentencetext>Nuff said?
Really, as if thats all thats needed from a comcast flak is a flat denial with no explanation as to why some users are having problems.
You sure you're cleared to know what the company is actually doing?
You sure every tech knows what management is doing?
Cause I don't think so.
And btw I post AC because I don't care to get an account.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269531</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271537</id>
	<title>No problems in central MA</title>
	<author>aaronl</author>
	<datestamp>1244541600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I'm a Comcast user in Lancaster, MA.  I had no problems connecting to anything, and my DNS was not being tampered with.  The only blocked services were Windows networking ports (135, 139, 445).</p></htmltext>
<tokenext>I 'm a Comcast user in Lancaster , MA .
I had no problems connecting to anything , and my DNS was not being tampered with .
The only blocked services were Windows networking ports ( 135 , 139 , 445 ) .</tokentext>
<sentencetext>I'm a Comcast user in Lancaster, MA.
I had no problems connecting to anything, and my DNS was not being tampered with.
The only blocked services were Windows networking ports (135, 139, 445).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269399</id>
	<title>Here's a permalink showing it may be happening...</title>
	<author>Anonymous</author>
	<datestamp>1244575920000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>1</modscore>
	<htmltext><p>http://netalyzr.icsi.berkeley.edu/restore/id=4b65aebb-18883-4ded0c2e-9922-4ace-8be5</p></htmltext>
<tokenext>http : //netalyzr.icsi.berkeley.edu/restore/id = 4b65aebb-18883-4ded0c2e-9922-4ace-8be5</tokentext>
<sentencetext>http://netalyzr.icsi.berkeley.edu/restore/id=4b65aebb-18883-4ded0c2e-9922-4ace-8be5</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269853</id>
	<title>Re:Port 53 Rerouted in Seattle :|</title>
	<author>aaronmarks</author>
	<datestamp>1244577780000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I have Comcast Business Class Internet in Seattle and I'm not re-rerouted; everything is working as it should. I internally have a split-horizon DNS setup where are DNS requests thare non-local are forwarded to OpenDNS's servers.</htmltext>
<tokenext>I have Comcast Business Class Internet in Seattle and I 'm not re-rerouted ; everything is working as it should .
I internally have a split-horizon DNS setup where are DNS requests thare non-local are forwarded to OpenDNS 's servers .</tokentext>
<sentencetext>I have Comcast Business Class Internet in Seattle and I'm not re-rerouted; everything is working as it should.
I internally have a split-horizon DNS setup where are DNS requests thare non-local are forwarded to OpenDNS's servers.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269633</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271941</id>
	<title>Not blocked in North Florida</title>
	<author>dr00g911</author>
	<datestamp>1244543640000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>They're not redirecting DNS in my area of North Florida, but</p><p>Apart from their God-awful downtime (about an hour a day at around 3am EST)...<nobr> <wbr></nobr>...and 1-hour almost instant disconnect if you're participating in a torrent they've flagged as unacceptable...<nobr> <wbr></nobr>...and terrible upstream speeds (about 45k / sec after the first 3 second burst)...<nobr> <wbr></nobr>...and random massive latency...<nobr> <wbr></nobr>...and questionable traffic shaping...<nobr> <wbr></nobr>...and "not really" unlimited internet...</p><p>They're ok-ish. Apart from being FUCKING EVIL. That said, the local cartel apparently hasn't gotten the same memo that caused TFA's seizure.</p><p>Ok, they suck compared to, say, Speakeasy in the old days, but AT&amp;T hasn't upgraded infrastructure in my neighborhood to support DSL, so Comcast is quite literally the only game in town. Yeah, I'm 5 miles outside of downtown and I can't get DSL here because up until a few years ago only poor folk lived in these old houses and it wasn't worth the time. Same reason there's no cable underground in Jacksonville's downtown... Cox cable (at the time) decided only poor folks lived there in the 70s when they last dug up the streets.</p><p>Anyhow, apart from blocking non-comcast SMTP, here's all Netalyzer anomalies:</p><p>RPC (Port 135) blocked<br>NetBIOS (Port 139) blocked<br>SMB (Port 445) blocked<br>DNS resolver (Comcast DNS): 1700ms (!!!)</p><p>Nothing I'd flag as unacceptable apart from the DNS latency. I learned to get my own SMTP host on an alternate port years ago as blocking port 25 is standard procedure on most ISPs.</p></htmltext>
<tokenext>They 're not redirecting DNS in my area of North Florida , butApart from their God-awful downtime ( about an hour a day at around 3am EST ) ... ...and 1-hour almost instant disconnect if you 're participating in a torrent they 've flagged as unacceptable... ...and terrible upstream speeds ( about 45k / sec after the first 3 second burst ) ... ...and random massive latency... ...and questionable traffic shaping... ...and " not really " unlimited internet...They 're ok-ish .
Apart from being FUCKING EVIL .
That said , the local cartel apparently has n't gotten the same memo that caused TFA 's seizure.Ok , they suck compared to , say , Speakeasy in the old days , but AT&amp;T has n't upgraded infrastructure in my neighborhood to support DSL , so Comcast is quite literally the only game in town .
Yeah , I 'm 5 miles outside of downtown and I ca n't get DSL here because up until a few years ago only poor folk lived in these old houses and it was n't worth the time .
Same reason there 's no cable underground in Jacksonville 's downtown... Cox cable ( at the time ) decided only poor folks lived there in the 70s when they last dug up the streets.Anyhow , apart from blocking non-comcast SMTP , here 's all Netalyzer anomalies : RPC ( Port 135 ) blockedNetBIOS ( Port 139 ) blockedSMB ( Port 445 ) blockedDNS resolver ( Comcast DNS ) : 1700ms ( ! ! !
) Nothing I 'd flag as unacceptable apart from the DNS latency .
I learned to get my own SMTP host on an alternate port years ago as blocking port 25 is standard procedure on most ISPs .</tokentext>
<sentencetext>They're not redirecting DNS in my area of North Florida, butApart from their God-awful downtime (about an hour a day at around 3am EST)... ...and 1-hour almost instant disconnect if you're participating in a torrent they've flagged as unacceptable... ...and terrible upstream speeds (about 45k / sec after the first 3 second burst)... ...and random massive latency... ...and questionable traffic shaping... ...and "not really" unlimited internet...They're ok-ish.
Apart from being FUCKING EVIL.
That said, the local cartel apparently hasn't gotten the same memo that caused TFA's seizure.Ok, they suck compared to, say, Speakeasy in the old days, but AT&amp;T hasn't upgraded infrastructure in my neighborhood to support DSL, so Comcast is quite literally the only game in town.
Yeah, I'm 5 miles outside of downtown and I can't get DSL here because up until a few years ago only poor folk lived in these old houses and it wasn't worth the time.
Same reason there's no cable underground in Jacksonville's downtown... Cox cable (at the time) decided only poor folks lived there in the 70s when they last dug up the streets.Anyhow, apart from blocking non-comcast SMTP, here's all Netalyzer anomalies:RPC (Port 135) blockedNetBIOS (Port 139) blockedSMB (Port 445) blockedDNS resolver (Comcast DNS): 1700ms (!!!
)Nothing I'd flag as unacceptable apart from the DNS latency.
I learned to get my own SMTP host on an alternate port years ago as blocking port 25 is standard procedure on most ISPs.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270387</id>
	<title>This information is false</title>
	<author>jlivingood</author>
	<datestamp>1244579760000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>This information is false, we do not intercept port 53 traffic.  The author of the linked blog should post their complete nslookup results, not the edited text they have posted.  We'd also like to know what NAT is being used (some of those proxy DNS in odd ways).

Jason

Comcast National Engineering &amp; Technical Operations</htmltext>
<tokenext>This information is false , we do not intercept port 53 traffic .
The author of the linked blog should post their complete nslookup results , not the edited text they have posted .
We 'd also like to know what NAT is being used ( some of those proxy DNS in odd ways ) .
Jason Comcast National Engineering &amp; Technical Operations</tokentext>
<sentencetext>This information is false, we do not intercept port 53 traffic.
The author of the linked blog should post their complete nslookup results, not the edited text they have posted.
We'd also like to know what NAT is being used (some of those proxy DNS in odd ways).
Jason

Comcast National Engineering &amp; Technical Operations</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273805</id>
	<title>Comcast ICSI Netalyzer link - Augusta, GA</title>
	<author>ccoder</author>
	<datestamp>1244556000000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>ICSI link from Augusta: <a href="http://netalyzr.icsi.berkeley.edu/restore/id=43ca3cda-24704-6729e1f9-944a-4263-9b69" title="berkeley.edu" rel="nofollow">http://netalyzr.icsi.berkeley.edu/restore/id=43ca3cda-24704-6729e1f9-944a-4263-9b69</a> [berkeley.edu]</htmltext>
<tokenext>ICSI link from Augusta : http : //netalyzr.icsi.berkeley.edu/restore/id = 43ca3cda-24704-6729e1f9-944a-4263-9b69 [ berkeley.edu ]</tokentext>
<sentencetext>ICSI link from Augusta: http://netalyzr.icsi.berkeley.edu/restore/id=43ca3cda-24704-6729e1f9-944a-4263-9b69 [berkeley.edu]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28279279</id>
	<title>Did any of you try a IP-Whois?</title>
	<author>Anonymous</author>
	<datestamp>1244647260000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Seriously? Did no one check the IP?  The IP Whois shows that IP in the redirect is owned by Earthlink, not Comcast.</p><p>http://ws.arin.net/whois/?queryinput=207.69.131.9</p><p>I hate Comcast as much as the next person (almost drove across town to defecate on their desks I was so pissed), but they are clearly not at fault here.</p><p>I'm surprised the Comcast "engineers" didn't pick up on this; or at the very least their spokesperson (read: spokesgirl).</p></htmltext>
<tokenext>Seriously ?
Did no one check the IP ?
The IP Whois shows that IP in the redirect is owned by Earthlink , not Comcast.http : //ws.arin.net/whois/ ? queryinput = 207.69.131.9I hate Comcast as much as the next person ( almost drove across town to defecate on their desks I was so pissed ) , but they are clearly not at fault here.I 'm surprised the Comcast " engineers " did n't pick up on this ; or at the very least their spokesperson ( read : spokesgirl ) .</tokentext>
<sentencetext>Seriously?
Did no one check the IP?
The IP Whois shows that IP in the redirect is owned by Earthlink, not Comcast.http://ws.arin.net/whois/?queryinput=207.69.131.9I hate Comcast as much as the next person (almost drove across town to defecate on their desks I was so pissed), but they are clearly not at fault here.I'm surprised the Comcast "engineers" didn't pick up on this; or at the very least their spokesperson (read: spokesgirl).</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269565</id>
	<title>Re:Fuck `Em All</title>
	<author>furby076</author>
	<datestamp>1244576520000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>So are you saying you wouldn't vote for them to win the Friendly Company Of the Year award?</htmltext>
<tokenext>So are you saying you would n't vote for them to win the Friendly Company Of the Year award ?</tokentext>
<sentencetext>So are you saying you wouldn't vote for them to win the Friendly Company Of the Year award?</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28277627</id>
	<title>Re:"Official Response"</title>
	<author>BitwiseX</author>
	<datestamp>1244637300000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>and yet if some guy came in and said "I'm Wil Wheaton!" you'd believe it!</htmltext>
<tokenext>and yet if some guy came in and said " I 'm Wil Wheaton !
" you 'd believe it !</tokentext>
<sentencetext>and yet if some guy came in and said "I'm Wil Wheaton!
" you'd believe it!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270179</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269243</id>
	<title>Re:Fuck `Em All</title>
	<author>danpritts</author>
	<datestamp>1244575500000</datestamp>
	<modclass>Flamebait</modclass>
	<modscore>0</modscore>
	<htmltext><p>glad to hear that comcast is morally equivalent to the perpetrators of the holocaust, who killed 12 million people in concentration camps.</p></htmltext>
<tokenext>glad to hear that comcast is morally equivalent to the perpetrators of the holocaust , who killed 12 million people in concentration camps .</tokentext>
<sentencetext>glad to hear that comcast is morally equivalent to the perpetrators of the holocaust, who killed 12 million people in concentration camps.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270969</id>
	<title>Re:"Official Response"</title>
	<author>Armarius</author>
	<datestamp>1244539140000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext>I can confirm that ComcastBonnie is an authorized Comcast rep. I've dealt with @comcastcares  on Twitter (Frank Eliason) and Bonnie is part of that team. Frank helped me cut through some BS with my local Comcast office about a year ago.  They look on the Internet for folks with complaints about Comcast, such as my blog post as year ago, and are pretty quick with the Twitter responses these days. And apparently Slashdot responses as well.

@LibraryMonk</htmltext>
<tokenext>I can confirm that ComcastBonnie is an authorized Comcast rep. I 've dealt with @ comcastcares on Twitter ( Frank Eliason ) and Bonnie is part of that team .
Frank helped me cut through some BS with my local Comcast office about a year ago .
They look on the Internet for folks with complaints about Comcast , such as my blog post as year ago , and are pretty quick with the Twitter responses these days .
And apparently Slashdot responses as well .
@ LibraryMonk</tokentext>
<sentencetext>I can confirm that ComcastBonnie is an authorized Comcast rep. I've dealt with @comcastcares  on Twitter (Frank Eliason) and Bonnie is part of that team.
Frank helped me cut through some BS with my local Comcast office about a year ago.
They look on the Internet for folks with complaints about Comcast, such as my blog post as year ago, and are pretty quick with the Twitter responses these days.
And apparently Slashdot responses as well.
@LibraryMonk</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270179</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269809</id>
	<title>Perhaps Comcast DNS proxy redirects non-responders</title>
	<author>Rene S. Hollan</author>
	<datestamp>1244577540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Hmm. I RTFA and it appears that the author's beef is that Comcast is responding where the responder is non-existent.</p><p>To replace unresolved DNS lookups with IP addresses of ad servers, Comcast has to proxy port 53 traffic, yes?</p><p>Well, if they do that, they can certainly redirect to their own DNS resolvers if the specified DNS resolver is non-responsive, just as easily as they can substitute an IP address when the specified resolver fails to resolve.</p><p>They can <b>also</b> redirect all port 53 traffic to their resolver, always, but it does not appear that they are doing this.</p><p>That doesn't strike me as evil as the article suggests. Still, they should disclose that they do this.</p></htmltext>
<tokenext>Hmm .
I RTFA and it appears that the author 's beef is that Comcast is responding where the responder is non-existent.To replace unresolved DNS lookups with IP addresses of ad servers , Comcast has to proxy port 53 traffic , yes ? Well , if they do that , they can certainly redirect to their own DNS resolvers if the specified DNS resolver is non-responsive , just as easily as they can substitute an IP address when the specified resolver fails to resolve.They can also redirect all port 53 traffic to their resolver , always , but it does not appear that they are doing this.That does n't strike me as evil as the article suggests .
Still , they should disclose that they do this .</tokentext>
<sentencetext>Hmm.
I RTFA and it appears that the author's beef is that Comcast is responding where the responder is non-existent.To replace unresolved DNS lookups with IP addresses of ad servers, Comcast has to proxy port 53 traffic, yes?Well, if they do that, they can certainly redirect to their own DNS resolvers if the specified DNS resolver is non-responsive, just as easily as they can substitute an IP address when the specified resolver fails to resolve.They can also redirect all port 53 traffic to their resolver, always, but it does not appear that they are doing this.That doesn't strike me as evil as the article suggests.
Still, they should disclose that they do this.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271647</id>
	<title>Not happening in South Florida</title>
	<author>Anonymous</author>
	<datestamp>1244542080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Verified not happening here via Comcast in Key West.</p></htmltext>
<tokenext>Verified not happening here via Comcast in Key West .</tokentext>
<sentencetext>Verified not happening here via Comcast in Key West.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269701</id>
	<title>Article is full of it</title>
	<author>Dog-Cow</author>
	<datestamp>1244577060000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I tested this with a server on a Comcast biz account (MI) going to a server on a non-Comcast network.  Worked fine.</p></htmltext>
<tokenext>I tested this with a server on a Comcast biz account ( MI ) going to a server on a non-Comcast network .
Worked fine .</tokentext>
<sentencetext>I tested this with a server on a Comcast biz account (MI) going to a server on a non-Comcast network.
Worked fine.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269505</id>
	<title>If they worked maybe more people would use them</title>
	<author>Xeriar</author>
	<datestamp>1244576280000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Was mostly a couple years ago, but even still, I had to keep a note of alternative DNS servers just in case Comcast's went on a fritz. Crazy annoying, and try explaining it to laymen!</p></htmltext>
<tokenext>Was mostly a couple years ago , but even still , I had to keep a note of alternative DNS servers just in case Comcast 's went on a fritz .
Crazy annoying , and try explaining it to laymen !</tokentext>
<sentencetext>Was mostly a couple years ago, but even still, I had to keep a note of alternative DNS servers just in case Comcast's went on a fritz.
Crazy annoying, and try explaining it to laymen!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28276903</id>
	<title>DNS issue = BULL****</title>
	<author>Anonymous</author>
	<datestamp>1244628360000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Hello i you want free comcast internet. goto a store buy a cable modem. do not subscribe the modem to comcast. plug the modem in. set it up. you will notice they gave you an outbound ip addy. now if you are on a router or your pc is directly hooked up goto any page. you will notice it redirected you to a self registration page. now on the pc/router change your dns server to 4.2.2.2 and 4.2.2.3 respectfully.</p><p>there you go free internet from comcast. nothing more than changing your dns. and if this works to get free inet then they are NOT screwing with your dns.</p><p>and to slashdot this site is getting worse by the day. all opinion articles.</p><p>starting to think you should rename the site to debatedot.org</p></htmltext>
<tokenext>Hello i you want free comcast internet .
goto a store buy a cable modem .
do not subscribe the modem to comcast .
plug the modem in .
set it up .
you will notice they gave you an outbound ip addy .
now if you are on a router or your pc is directly hooked up goto any page .
you will notice it redirected you to a self registration page .
now on the pc/router change your dns server to 4.2.2.2 and 4.2.2.3 respectfully.there you go free internet from comcast .
nothing more than changing your dns .
and if this works to get free inet then they are NOT screwing with your dns.and to slashdot this site is getting worse by the day .
all opinion articles.starting to think you should rename the site to debatedot.org</tokentext>
<sentencetext>Hello i you want free comcast internet.
goto a store buy a cable modem.
do not subscribe the modem to comcast.
plug the modem in.
set it up.
you will notice they gave you an outbound ip addy.
now if you are on a router or your pc is directly hooked up goto any page.
you will notice it redirected you to a self registration page.
now on the pc/router change your dns server to 4.2.2.2 and 4.2.2.3 respectfully.there you go free internet from comcast.
nothing more than changing your dns.
and if this works to get free inet then they are NOT screwing with your dns.and to slashdot this site is getting worse by the day.
all opinion articles.starting to think you should rename the site to debatedot.org</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269725</id>
	<title>BS?</title>
	<author>singingjim1</author>
	<datestamp>1244577180000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>So basically this story is total bullshit? Here on Slashdot? Shocking. Even if it was true who does this affect?  About 20 of you out there that would even notice? For the average user this makes absolutely no difference in our service. Yes, I'm just an average user. Sorry! Sorry I'm just an average user!</htmltext>
<tokenext>So basically this story is total bullshit ?
Here on Slashdot ?
Shocking. Even if it was true who does this affect ?
About 20 of you out there that would even notice ?
For the average user this makes absolutely no difference in our service .
Yes , I 'm just an average user .
Sorry ! Sorry I 'm just an average user !</tokentext>
<sentencetext>So basically this story is total bullshit?
Here on Slashdot?
Shocking. Even if it was true who does this affect?
About 20 of you out there that would even notice?
For the average user this makes absolutely no difference in our service.
Yes, I'm just an average user.
Sorry! Sorry I'm just an average user!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28277199</id>
	<title>Re:Is this happening for ANYONE?</title>
	<author>Anonymous</author>
	<datestamp>1244631780000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>come on, someone has to create slashdotminuskdawson.org</p></htmltext>
<tokenext>come on , someone has to create slashdotminuskdawson.org</tokentext>
<sentencetext>come on, someone has to create slashdotminuskdawson.org</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269435</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271747</id>
	<title>Comcast in Ca.</title>
	<author>PPNSteve</author>
	<datestamp>1244542680000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext>We're also on Comcast in Cali and use 3rd party DNS.. without issue.
Comcast isn't messing with any of our port 53 traffic either:
DNS Tests

Restricted domain DNS lookup: OK
We are able to successfully lookup a name which resolves to the same IP address as our webserver. This means we are able to conduct many of the tests on your DNS server.

Unrestricted domain DNS lookup: OK
We are able to successfully lookup arbitrary names from within the Java applet. This means we are able to conduct all test on your DNS server.

DNS resolver address: OK
The IP address of your ISP's DNS Resolver is 209.244.1.19, which resolves to ics3.SanJose1.Level3.net.

DNS resolver properties: Lookup latency: 120ms
Your ISP's DNS resolver requires 120 msec to conduct an external lookup, and 110 msec to lookup an item in the cache.
Your resolver is using QTYPE=A for default queries.
Your resolver is not automatically performing IPv6 queries.
Your DNS resolver requests DNSSEC records.
Your DNS resolver will accept DNS packets of up to 4096 bytes.
Your DNS resolver can successfully receive a large (&gt;1500 byte) DNS response.
Your resolver does not use 0x20 randomization, but will pass names in a case-sensitive manner.
Your ISP's DNS resolver respects a TTL of 0 seconds.
Your ISP's DNS resolver respects a TTL of 1 seconds.

DNS glue policy: OK
Your ISP's DNS resolver does not accept generic additional (glue) records -- good.
Your ISP's DNS resolver accepts additional (glue) records for nameservers located in subdomains of the queried domain.
Your ISP's DNS resolver does not follow CNAMEs.

DNS resolver port randomization: OK
Your ISP's DNS resolver properly randomizes its local port number.
The following graph shows DNS requests on the x-axis and the detected source ports on the y-axis.

port sequence plot

DNS lookups of popular domains: OK
74 of 74 popular names were resolved successfully. Show all names.
In the following table reverse lookups that failed but for which a Start Of Authority (SOA) entry indicated correct name associations are shown using an "X", followed by the SOA entry. Absence of both IP address and reverse name indicates failed forward lookups.
Name 	IP Address 	Reverse Name/SOA
www.abbey.co.uk 	165.160.13.20 	X (pdns1.cscdns.net)
ad.doubleclick.net 	209.62.176.153 	eqnjmegaadvip3.doubleclick.net
www.alliance-leicester.co.uk 	194.130.105.121 	X (alice.ioko365.com)
www.amazon.com 	72.21.210.250 	210-250.amazon.com
www.ameritrade.com 	204.58.27.97 	beta-new.tdameritrade.com
www.bankofamerica.com 	171.161.161.173 	www.bankofamerica.com
www.bankofscotland.co.uk 	195.171.171.21 	X (ns0.bt.net)
www.bankofthewest.com 	207.114.194.101 	X (dns1a.bankofthewest.com)
www.barclays.co.uk 	213.219.1.141 	X (dns1.lon7.telecityredbus.net)
www.capitalone.com 	208.80.50.112 	X (chia.arin.NET)
www.chase.com 	159.53.60.105 	X (ns1.jpmorganchase.com)
chaseonline.chase.com 	159.53.60.54 	resources-cdc1.chase.com
www.citi.com 	192.193.217.200 	X (ns.citicorp.com)
www.citibank.com 	192.193.217.200 	X (ns.citicorp.com)
www.citimortgage.com 	192.193.218.222 	X (ns.citicorp.com)
www.cnn.com 	157.166.224.26 	www.cnn.com
www.desjardins.com 	142.195.128.44 	desjardins.com
www.deutsche-bank.de 	217.73.49.24 	www.deutsche-bank.de
www.e-gold.com 	209.200.169.10 	unknown.prolexic.com
www.ebay.com 	66.135.200.145 	hp-core.ebay.com
www.etrade.com 	12.153.224.22 	etrade.com
www.f-secure.com 	8.18.65.65 	X (ns2.Level3.net)
www.facebook.com 	69.63.180.12 	www2.02.07.facebook.com
www.fdic.gov 	192.147.69.84 	www.fdic.gov
www.friendfinder.com 	208.88.180.81 	X (ii53-30.friendfinderinc.com)
www.geocities.com 	98.137.46.72 	intl1.geo.vip.sp2.yahoo.com
www.google.com 	74.125.155.99 	px-in-f99.google.com
www.halifax.co.uk 	62.172.43.225 	www.halifax.co.uk
www.hsbc.co.uk 	193.108.74.126 	X (ns3.hsbc.com)
www.jpmorganchase.com 	159.53.60.166 	X (ns1.jpmorganchase.com)
www.lloydstsb.com 	193.34.230.181 	X (ns2.lloydstsb.co.uk)
mail.google.com 	74.125.155.17 	px-in-f17.google.com
mail.live.com 	64.4.20.174 	dp1.mail.live.com
mail.yahoo.com 	66.163.169.186 	l1.login.vip.sp1.y</htmltext>
<tokenext>We 're also on Comcast in Cali and use 3rd party DNS.. without issue .
Comcast is n't messing with any of our port 53 traffic either : DNS Tests Restricted domain DNS lookup : OK We are able to successfully lookup a name which resolves to the same IP address as our webserver .
This means we are able to conduct many of the tests on your DNS server .
Unrestricted domain DNS lookup : OK We are able to successfully lookup arbitrary names from within the Java applet .
This means we are able to conduct all test on your DNS server .
DNS resolver address : OK The IP address of your ISP 's DNS Resolver is 209.244.1.19 , which resolves to ics3.SanJose1.Level3.net .
DNS resolver properties : Lookup latency : 120ms Your ISP 's DNS resolver requires 120 msec to conduct an external lookup , and 110 msec to lookup an item in the cache .
Your resolver is using QTYPE = A for default queries .
Your resolver is not automatically performing IPv6 queries .
Your DNS resolver requests DNSSEC records .
Your DNS resolver will accept DNS packets of up to 4096 bytes .
Your DNS resolver can successfully receive a large ( &gt; 1500 byte ) DNS response .
Your resolver does not use 0x20 randomization , but will pass names in a case-sensitive manner .
Your ISP 's DNS resolver respects a TTL of 0 seconds .
Your ISP 's DNS resolver respects a TTL of 1 seconds .
DNS glue policy : OK Your ISP 's DNS resolver does not accept generic additional ( glue ) records -- good .
Your ISP 's DNS resolver accepts additional ( glue ) records for nameservers located in subdomains of the queried domain .
Your ISP 's DNS resolver does not follow CNAMEs .
DNS resolver port randomization : OK Your ISP 's DNS resolver properly randomizes its local port number .
The following graph shows DNS requests on the x-axis and the detected source ports on the y-axis .
port sequence plot DNS lookups of popular domains : OK 74 of 74 popular names were resolved successfully .
Show all names .
In the following table reverse lookups that failed but for which a Start Of Authority ( SOA ) entry indicated correct name associations are shown using an " X " , followed by the SOA entry .
Absence of both IP address and reverse name indicates failed forward lookups .
Name IP Address Reverse Name/SOA www.abbey.co.uk 165.160.13.20 X ( pdns1.cscdns.net ) ad.doubleclick.net 209.62.176.153 eqnjmegaadvip3.doubleclick.net www.alliance-leicester.co.uk 194.130.105.121 X ( alice.ioko365.com ) www.amazon.com 72.21.210.250 210-250.amazon.com www.ameritrade.com 204.58.27.97 beta-new.tdameritrade.com www.bankofamerica.com 171.161.161.173 www.bankofamerica.com www.bankofscotland.co.uk 195.171.171.21 X ( ns0.bt.net ) www.bankofthewest.com 207.114.194.101 X ( dns1a.bankofthewest.com ) www.barclays.co.uk 213.219.1.141 X ( dns1.lon7.telecityredbus.net ) www.capitalone.com 208.80.50.112 X ( chia.arin.NET ) www.chase.com 159.53.60.105 X ( ns1.jpmorganchase.com ) chaseonline.chase.com 159.53.60.54 resources-cdc1.chase.com www.citi.com 192.193.217.200 X ( ns.citicorp.com ) www.citibank.com 192.193.217.200 X ( ns.citicorp.com ) www.citimortgage.com 192.193.218.222 X ( ns.citicorp.com ) www.cnn.com 157.166.224.26 www.cnn.com www.desjardins.com 142.195.128.44 desjardins.com www.deutsche-bank.de 217.73.49.24 www.deutsche-bank.de www.e-gold.com 209.200.169.10 unknown.prolexic.com www.ebay.com 66.135.200.145 hp-core.ebay.com www.etrade.com 12.153.224.22 etrade.com www.f-secure.com 8.18.65.65 X ( ns2.Level3.net ) www.facebook.com 69.63.180.12 www2.02.07.facebook.com www.fdic.gov 192.147.69.84 www.fdic.gov www.friendfinder.com 208.88.180.81 X ( ii53-30.friendfinderinc.com ) www.geocities.com 98.137.46.72 intl1.geo.vip.sp2.yahoo.com www.google.com 74.125.155.99 px-in-f99.google.com www.halifax.co.uk 62.172.43.225 www.halifax.co.uk www.hsbc.co.uk 193.108.74.126 X ( ns3.hsbc.com ) www.jpmorganchase.com 159.53.60.166 X ( ns1.jpmorganchase.com ) www.lloydstsb.com 193.34.230.181 X ( ns2.lloydstsb.co.uk ) mail.google.com 74.125.155.17 px-in-f17.google.com mail.live.com 64.4.20.174 dp1.mail.live.com mail.yahoo.com 66.163.169.186 l1.login.vip.sp1.y</tokentext>
<sentencetext>We're also on Comcast in Cali and use 3rd party DNS.. without issue.
Comcast isn't messing with any of our port 53 traffic either:
DNS Tests

Restricted domain DNS lookup: OK
We are able to successfully lookup a name which resolves to the same IP address as our webserver.
This means we are able to conduct many of the tests on your DNS server.
Unrestricted domain DNS lookup: OK
We are able to successfully lookup arbitrary names from within the Java applet.
This means we are able to conduct all test on your DNS server.
DNS resolver address: OK
The IP address of your ISP's DNS Resolver is 209.244.1.19, which resolves to ics3.SanJose1.Level3.net.
DNS resolver properties: Lookup latency: 120ms
Your ISP's DNS resolver requires 120 msec to conduct an external lookup, and 110 msec to lookup an item in the cache.
Your resolver is using QTYPE=A for default queries.
Your resolver is not automatically performing IPv6 queries.
Your DNS resolver requests DNSSEC records.
Your DNS resolver will accept DNS packets of up to 4096 bytes.
Your DNS resolver can successfully receive a large (&gt;1500 byte) DNS response.
Your resolver does not use 0x20 randomization, but will pass names in a case-sensitive manner.
Your ISP's DNS resolver respects a TTL of 0 seconds.
Your ISP's DNS resolver respects a TTL of 1 seconds.
DNS glue policy: OK
Your ISP's DNS resolver does not accept generic additional (glue) records -- good.
Your ISP's DNS resolver accepts additional (glue) records for nameservers located in subdomains of the queried domain.
Your ISP's DNS resolver does not follow CNAMEs.
DNS resolver port randomization: OK
Your ISP's DNS resolver properly randomizes its local port number.
The following graph shows DNS requests on the x-axis and the detected source ports on the y-axis.
port sequence plot

DNS lookups of popular domains: OK
74 of 74 popular names were resolved successfully.
Show all names.
In the following table reverse lookups that failed but for which a Start Of Authority (SOA) entry indicated correct name associations are shown using an "X", followed by the SOA entry.
Absence of both IP address and reverse name indicates failed forward lookups.
Name 	IP Address 	Reverse Name/SOA
www.abbey.co.uk 	165.160.13.20 	X (pdns1.cscdns.net)
ad.doubleclick.net 	209.62.176.153 	eqnjmegaadvip3.doubleclick.net
www.alliance-leicester.co.uk 	194.130.105.121 	X (alice.ioko365.com)
www.amazon.com 	72.21.210.250 	210-250.amazon.com
www.ameritrade.com 	204.58.27.97 	beta-new.tdameritrade.com
www.bankofamerica.com 	171.161.161.173 	www.bankofamerica.com
www.bankofscotland.co.uk 	195.171.171.21 	X (ns0.bt.net)
www.bankofthewest.com 	207.114.194.101 	X (dns1a.bankofthewest.com)
www.barclays.co.uk 	213.219.1.141 	X (dns1.lon7.telecityredbus.net)
www.capitalone.com 	208.80.50.112 	X (chia.arin.NET)
www.chase.com 	159.53.60.105 	X (ns1.jpmorganchase.com)
chaseonline.chase.com 	159.53.60.54 	resources-cdc1.chase.com
www.citi.com 	192.193.217.200 	X (ns.citicorp.com)
www.citibank.com 	192.193.217.200 	X (ns.citicorp.com)
www.citimortgage.com 	192.193.218.222 	X (ns.citicorp.com)
www.cnn.com 	157.166.224.26 	www.cnn.com
www.desjardins.com 	142.195.128.44 	desjardins.com
www.deutsche-bank.de 	217.73.49.24 	www.deutsche-bank.de
www.e-gold.com 	209.200.169.10 	unknown.prolexic.com
www.ebay.com 	66.135.200.145 	hp-core.ebay.com
www.etrade.com 	12.153.224.22 	etrade.com
www.f-secure.com 	8.18.65.65 	X (ns2.Level3.net)
www.facebook.com 	69.63.180.12 	www2.02.07.facebook.com
www.fdic.gov 	192.147.69.84 	www.fdic.gov
www.friendfinder.com 	208.88.180.81 	X (ii53-30.friendfinderinc.com)
www.geocities.com 	98.137.46.72 	intl1.geo.vip.sp2.yahoo.com
www.google.com 	74.125.155.99 	px-in-f99.google.com
www.halifax.co.uk 	62.172.43.225 	www.halifax.co.uk
www.hsbc.co.uk 	193.108.74.126 	X (ns3.hsbc.com)
www.jpmorganchase.com 	159.53.60.166 	X (ns1.jpmorganchase.com)
www.lloydstsb.com 	193.34.230.181 	X (ns2.lloydstsb.co.uk)
mail.google.com 	74.125.155.17 	px-in-f17.google.com
mail.live.com 	64.4.20.174 	dp1.mail.live.com
mail.yahoo.com 	66.163.169.186 	l1.login.vip.sp1.y</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269815</id>
	<title>Comcast isn't sending you to a search for porn</title>
	<author>MattW</author>
	<datestamp>1244577600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>Non-authoritative answer:<br>Name:    comcast.sucks.com<br>Address: 207.69.131.9<br>Name:    comcast.sucks.com<br>Address: 207.69.131.10</p></div></blockquote><blockquote><div><p>[matt@manticore ~]$ whois 207.69.131.10<br>[Querying whois.arin.net]<br>[whois.arin.net]</p><p>OrgName:    <b>EarthLink, Inc. </b><br>OrgID:      ERMS<br>Address:    1375 PEACHTREE ST, LEVEL A<br>City:       ATLANTA<br>StateProv:  GA<br>PostalCode: 30309<br>Country:    US</p><p>NetRange:   <b>207.69.0.0 - 207.69.255.255</b><br>CIDR:       207.69.0.0/16<br>NetName:    EARTHLINK2000-D<br>NetHandle:  NET-207-69-0-0-1<br>Parent:     NET-207-0-0-0-0<br>NetType:    Direct Allocation<br>NameServer: ITCHY.EARTHLINK.NET<br>NameServer: SCRATCHY.EARTHLINK.NET<br>Comment:<br>RegDate:    1998-10-20<br>Updated:    2007-03-30</p><p>RTechHandle: DAE4-ARIN<br>RTechName:   Domain Administrator, Administrator<br>RTechPhone:  +1-404-815-0770<br>RTechEmail:  arinpoc@corp.earthlink.net</p><p>OrgAbuseHandle: ABUSE60-ARIN<br>OrgAbuseName:   ABUSE TEAM<br>OrgAbusePhone:  +1-404-815-0770<br>OrgAbuseEmail:  abuse@abuse.earthlink.net</p><p>OrgTechHandle: ELNK-ORG-ARIN<br>OrgTechName:   EarthLink, Inc.<br>OrgTechPhone:  +1-404-815-0770<br>OrgTechEmail:  arin\_tech@lists.corp.earthlink.net</p></div></blockquote><p>So I'm thinking... ok, if Comcast hijacked your dns, why would they send it to an earthlink IP?</p><p>So I navigate to 207.69.131.9...</p><p>And I get javascript redirecting me to:</p><p><a href="http://earthlink-help.com/main?AddInType=Bdns&amp;Version=1.4.11&amp;FailureMode=1&amp;ParticipantID=xj6e3468k634hy3945zg3zkhfn7zfgf6&amp;ClientLocation=us&amp;Referer=&amp;FailedURI=http\%3A\%2F\%2F207.69.131.9\%2F&amp;SearchQuery=" title="earthlink-help.com">http://earthlink-help.com/main?AddInType=Bdns&amp;Version=1.4.11&amp;FailureMode=1&amp;ParticipantID=xj6e3468k634hy3945zg3zkhfn7zfgf6&amp;ClientLocation=us&amp;Referer=&amp;FailedURI=http\%3A\%2F\%2F207.69.131.9\%2F&amp;SearchQuery=</a> [earthlink-help.com]</p><p>Where I get some kind of branded search and this:</p><blockquote><div><p>We are sorry, <b>porn</b> cannot be found.<br>We suggest that you check the spelling of the web address or try a different search term.</p></div></blockquote><p>I'm not sure why Comcast would redirect you to Earthlink in the first place... but even if they did, I seriously doubt they'd redirect you to a search for pr0n in particular. Time to dig a little more.</p></div>
	</htmltext>
<tokenext>Non-authoritative answer : Name : comcast.sucks.comAddress : 207.69.131.9Name : comcast.sucks.comAddress : 207.69.131.10 [ matt @ manticore ~ ] $ whois 207.69.131.10 [ Querying whois.arin.net ] [ whois.arin.net ] OrgName : EarthLink , Inc. OrgID : ERMSAddress : 1375 PEACHTREE ST , LEVEL ACity : ATLANTAStateProv : GAPostalCode : 30309Country : USNetRange : 207.69.0.0 - 207.69.255.255CIDR : 207.69.0.0/16NetName : EARTHLINK2000-DNetHandle : NET-207-69-0-0-1Parent : NET-207-0-0-0-0NetType : Direct AllocationNameServer : ITCHY.EARTHLINK.NETNameServer : SCRATCHY.EARTHLINK.NETComment : RegDate : 1998-10-20Updated : 2007-03-30RTechHandle : DAE4-ARINRTechName : Domain Administrator , AdministratorRTechPhone : + 1-404-815-0770RTechEmail : arinpoc @ corp.earthlink.netOrgAbuseHandle : ABUSE60-ARINOrgAbuseName : ABUSE TEAMOrgAbusePhone : + 1-404-815-0770OrgAbuseEmail : abuse @ abuse.earthlink.netOrgTechHandle : ELNK-ORG-ARINOrgTechName : EarthLink , Inc.OrgTechPhone : + 1-404-815-0770OrgTechEmail : arin \ _tech @ lists.corp.earthlink.netSo I 'm thinking... ok , if Comcast hijacked your dns , why would they send it to an earthlink IP ? So I navigate to 207.69.131.9...And I get javascript redirecting me to : http : //earthlink-help.com/main ? AddInType = Bdns&amp;Version = 1.4.11&amp;FailureMode = 1&amp;ParticipantID = xj6e3468k634hy3945zg3zkhfn7zfgf6&amp;ClientLocation = us&amp;Referer = &amp;FailedURI = http \ % 3A \ % 2F \ % 2F207.69.131.9 \ % 2F&amp;SearchQuery = [ earthlink-help.com ] Where I get some kind of branded search and this : We are sorry , porn can not be found.We suggest that you check the spelling of the web address or try a different search term.I 'm not sure why Comcast would redirect you to Earthlink in the first place... but even if they did , I seriously doubt they 'd redirect you to a search for pr0n in particular .
Time to dig a little more .</tokentext>
<sentencetext>Non-authoritative answer:Name:    comcast.sucks.comAddress: 207.69.131.9Name:    comcast.sucks.comAddress: 207.69.131.10[matt@manticore ~]$ whois 207.69.131.10[Querying whois.arin.net][whois.arin.net]OrgName:    EarthLink, Inc. OrgID:      ERMSAddress:    1375 PEACHTREE ST, LEVEL ACity:       ATLANTAStateProv:  GAPostalCode: 30309Country:    USNetRange:   207.69.0.0 - 207.69.255.255CIDR:       207.69.0.0/16NetName:    EARTHLINK2000-DNetHandle:  NET-207-69-0-0-1Parent:     NET-207-0-0-0-0NetType:    Direct AllocationNameServer: ITCHY.EARTHLINK.NETNameServer: SCRATCHY.EARTHLINK.NETComment:RegDate:    1998-10-20Updated:    2007-03-30RTechHandle: DAE4-ARINRTechName:   Domain Administrator, AdministratorRTechPhone:  +1-404-815-0770RTechEmail:  arinpoc@corp.earthlink.netOrgAbuseHandle: ABUSE60-ARINOrgAbuseName:   ABUSE TEAMOrgAbusePhone:  +1-404-815-0770OrgAbuseEmail:  abuse@abuse.earthlink.netOrgTechHandle: ELNK-ORG-ARINOrgTechName:   EarthLink, Inc.OrgTechPhone:  +1-404-815-0770OrgTechEmail:  arin\_tech@lists.corp.earthlink.netSo I'm thinking... ok, if Comcast hijacked your dns, why would they send it to an earthlink IP?So I navigate to 207.69.131.9...And I get javascript redirecting me to:http://earthlink-help.com/main?AddInType=Bdns&amp;Version=1.4.11&amp;FailureMode=1&amp;ParticipantID=xj6e3468k634hy3945zg3zkhfn7zfgf6&amp;ClientLocation=us&amp;Referer=&amp;FailedURI=http\%3A\%2F\%2F207.69.131.9\%2F&amp;SearchQuery= [earthlink-help.com]Where I get some kind of branded search and this:We are sorry, porn cannot be found.We suggest that you check the spelling of the web address or try a different search term.I'm not sure why Comcast would redirect you to Earthlink in the first place... but even if they did, I seriously doubt they'd redirect you to a search for pr0n in particular.
Time to dig a little more.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270259</id>
	<title>Yes!</title>
	<author>porky\_pig\_jr</author>
	<datestamp>1244579340000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Getting 'response from unautorized servers' when I do nslookup. The servers are comcast servers. Can't reach *lot's* of site, by the way, fine going via my emergency alternate route (dial in, just think of that!). Massachusetts located.</p></htmltext>
<tokenext>Getting 'response from unautorized servers ' when I do nslookup .
The servers are comcast servers .
Ca n't reach * lot 's * of site , by the way , fine going via my emergency alternate route ( dial in , just think of that ! ) .
Massachusetts located .</tokentext>
<sentencetext>Getting 'response from unautorized servers' when I do nslookup.
The servers are comcast servers.
Can't reach *lot's* of site, by the way, fine going via my emergency alternate route (dial in, just think of that!).
Massachusetts located.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269619</id>
	<title>Everything is dandy in my town</title>
	<author>eclectro</author>
	<datestamp>1244576700000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>That is, <a href="http://www.comcasttown.com/" title="comcasttown.com">Comcast Town</a> [comcasttown.com]</p></htmltext>
<tokenext>That is , Comcast Town [ comcasttown.com ]</tokentext>
<sentencetext>That is, Comcast Town [comcasttown.com]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269801</id>
	<title>Re:Fuck `Em All</title>
	<author>Anonymous</author>
	<datestamp>1244577480000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Censorship was a big part of how the nazis got to be so in control.  Things like this are the first steps in censorship.</p></htmltext>
<tokenext>Censorship was a big part of how the nazis got to be so in control .
Things like this are the first steps in censorship .</tokentext>
<sentencetext>Censorship was a big part of how the nazis got to be so in control.
Things like this are the first steps in censorship.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269171</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270009</id>
	<title>Re:Fuck `Em All</title>
	<author>Abreu</author>
	<datestamp>1244578440000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Yeah, I hear his paintings were atrocious!</p></htmltext>
<tokenext>Yeah , I hear his paintings were atrocious !</tokentext>
<sentencetext>Yeah, I hear his paintings were atrocious!</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269271</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269605</id>
	<title>Federal Wiretapping Laws</title>
	<author>Anonymous</author>
	<datestamp>1244576700000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>If this is true, wouldn't it be a violation of the Federal Wiretapping Act? They are certainly intercepting electronic communications, and worse yet, they are redirecting them and sending their own response. Is anyone an actual lawyer that is familiar enough with the act to comment intelligently on whether this is a violation or not?</p></htmltext>
<tokenext>If this is true , would n't it be a violation of the Federal Wiretapping Act ?
They are certainly intercepting electronic communications , and worse yet , they are redirecting them and sending their own response .
Is anyone an actual lawyer that is familiar enough with the act to comment intelligently on whether this is a violation or not ?</tokentext>
<sentencetext>If this is true, wouldn't it be a violation of the Federal Wiretapping Act?
They are certainly intercepting electronic communications, and worse yet, they are redirecting them and sending their own response.
Is anyone an actual lawyer that is familiar enough with the act to comment intelligently on whether this is a violation or not?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269539</id>
	<title>Re:Security</title>
	<author>Anonymous</author>
	<datestamp>1244576460000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>They could be doing this for security reasons, to prevent DNS domain hijacking.</p></div><p>That could be true.  After all anyone else could hijack the DNS request right after comcast hijacks it first... Oh wait</p></div>
	</htmltext>
<tokenext>They could be doing this for security reasons , to prevent DNS domain hijacking.That could be true .
After all anyone else could hijack the DNS request right after comcast hijacks it first... Oh wait</tokentext>
<sentencetext>They could be doing this for security reasons, to prevent DNS domain hijacking.That could be true.
After all anyone else could hijack the DNS request right after comcast hijacks it first... Oh wait
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269147</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269115</id>
	<title>I really am hoping this is NOT a gullibility test</title>
	<author>Anonymous</author>
	<datestamp>1244575140000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>2</modscore>
	<htmltext><p>My connection is comcast for biz-- go crazy- I took out my last subnet</p><p>The ICSI Netalyzr Beta<br>Introduction  Analysis  Results<br>Result Summary<br>74-92-106-XXX-Philadelphia.hfc.comcastbusiness.net / 74.92.106.XXX<br>Recorded at 14:15 EDT (18:15 UTC) on Tue, June 09 2009. Permalink. Transcript.<br>Noteworthy Events<br>Minor Aberrations</p><p>Certain protocols are blocked in outbound traffic<br>Address-based Tests<br>NAT detection: NAT Detected</p><p>Your global IP address is 74.92.106.XXX while your local one is 192.168.15.XX. You are behind a NAT. Your local address is in unroutable address space.</p><p>Your NAT renumbers TCP source ports sequentially. The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis.</p><p>DNS-based host information: OK</p><p>You are not a Tor exit node for HTTP traffic.<br>You are not listed on any Spamhaus blacklists.<br>The SORBS DUHL believes you are using a statically assigned IP address.<br>Reachability Tests<br>General connectivity: Note</p><p>Basic UDP access is available.<br>Direct UDP access to remote DNS servers (port 53) is allowed.<br>The applet was also able to directly request a large DNS response.<br>Direct UDP access to remote MSSQL servers (port 1434) is allowed.<br>Direct TCP connections to remote FTP servers (port 21) failed.<br>This is commonly due to how a NAT or firewall handles FTP traffic, as FTP causes unique problems when developing NATs and firewalls.<br>Direct TCP access to remote SSH servers (port 22) is allowed.<br>Direct TCP access to remote SMTP servers (port 25) is allowed.<br>Direct TCP access to remote DNS servers (port 53) is allowed.<br>Direct TCP access to remote HTTP servers (port 80) is allowed.<br>Direct TCP access to remote POP servers (port 110) is allowed.<br>Direct TCP access to remote RPC servers (port 135) is blocked.<br>This is probably for security reasons, as this protocol is generally not designed for use outside the local network.<br>Direct TCP access to remote NetBIOS servers (port 139) is blocked.<br>This is probably for security reasons, as this protocol is generally not designed for use outside the local network.<br>Direct TCP access to remote IMAP servers (port 143) is allowed.<br>Direct TCP access to remote SNMP servers (port 161) is allowed.<br>Direct TCP access to remote HTTPS servers (port 443) is allowed.<br>Direct TCP access to remote SMB servers (port 445) is blocked.<br>This is probably for security reasons, as this protocol is generally not designed for use outside the local network.<br>Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.<br>Direct TCP access to remote secure IMAP servers (port 585) is allowed.<br>Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.<br>Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.<br>Direct TCP access to remote POP/SSL servers (port 995) is allowed.<br>Direct TCP access to remote SIP servers (port 5060) is allowed.<br>Direct TCP access to remote BitTorrent servers (port 6881) is allowed.<br>Network Access Link Properties<br>Network latency measurements: Latency: 26ms Loss: 0.0\%</p><p>The round-trip time (RTT) between your computer and our server is 26 msec, which is good.<br>We recorded no packet loss between your system and our server.<br>TCP connection setup latency: 29ms</p><p>The time it takes your computer to set up a TCP connection with our server is 29 msec, which is good.<br>Network bandwidth measurements: Upload 4.3 Mbit/sec, Download 7.1 Mbit/sec</p><p>Your Uplink: We measured your uplink's sending bandwidth at 4.3 Mbit/sec. This level of bandwidth works well for many users.<br>Your Downlink: We measured your downlink's receiving bandwidth at 7.1 Mbit/sec. This level of bandwidth works well for many users.<br>Network buffer measurements: Uplink 229 ms, Downlink 220 ms</p><p>We estimate your uplink as having 230 msec of buffering. This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.<br>We estimate your</p></htmltext>
<tokenext>My connection is comcast for biz-- go crazy- I took out my last subnetThe ICSI Netalyzr BetaIntroduction Analysis ResultsResult Summary74-92-106-XXX-Philadelphia.hfc.comcastbusiness.net / 74.92.106.XXXRecorded at 14 : 15 EDT ( 18 : 15 UTC ) on Tue , June 09 2009 .
Permalink. Transcript.Noteworthy EventsMinor AberrationsCertain protocols are blocked in outbound trafficAddress-based TestsNAT detection : NAT DetectedYour global IP address is 74.92.106.XXX while your local one is 192.168.15.XX .
You are behind a NAT .
Your local address is in unroutable address space.Your NAT renumbers TCP source ports sequentially .
The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis.DNS-based host information : OKYou are not a Tor exit node for HTTP traffic.You are not listed on any Spamhaus blacklists.The SORBS DUHL believes you are using a statically assigned IP address.Reachability TestsGeneral connectivity : NoteBasic UDP access is available.Direct UDP access to remote DNS servers ( port 53 ) is allowed.The applet was also able to directly request a large DNS response.Direct UDP access to remote MSSQL servers ( port 1434 ) is allowed.Direct TCP connections to remote FTP servers ( port 21 ) failed.This is commonly due to how a NAT or firewall handles FTP traffic , as FTP causes unique problems when developing NATs and firewalls.Direct TCP access to remote SSH servers ( port 22 ) is allowed.Direct TCP access to remote SMTP servers ( port 25 ) is allowed.Direct TCP access to remote DNS servers ( port 53 ) is allowed.Direct TCP access to remote HTTP servers ( port 80 ) is allowed.Direct TCP access to remote POP servers ( port 110 ) is allowed.Direct TCP access to remote RPC servers ( port 135 ) is blocked.This is probably for security reasons , as this protocol is generally not designed for use outside the local network.Direct TCP access to remote NetBIOS servers ( port 139 ) is blocked.This is probably for security reasons , as this protocol is generally not designed for use outside the local network.Direct TCP access to remote IMAP servers ( port 143 ) is allowed.Direct TCP access to remote SNMP servers ( port 161 ) is allowed.Direct TCP access to remote HTTPS servers ( port 443 ) is allowed.Direct TCP access to remote SMB servers ( port 445 ) is blocked.This is probably for security reasons , as this protocol is generally not designed for use outside the local network.Direct TCP access to remote SMTP/SSL servers ( port 465 ) is allowed.Direct TCP access to remote secure IMAP servers ( port 585 ) is allowed.Direct TCP access to remote authenticated SMTP servers ( port 587 ) is allowed.Direct TCP access to remote IMAP/SSL servers ( port 993 ) is allowed.Direct TCP access to remote POP/SSL servers ( port 995 ) is allowed.Direct TCP access to remote SIP servers ( port 5060 ) is allowed.Direct TCP access to remote BitTorrent servers ( port 6881 ) is allowed.Network Access Link PropertiesNetwork latency measurements : Latency : 26ms Loss : 0.0 \ % The round-trip time ( RTT ) between your computer and our server is 26 msec , which is good.We recorded no packet loss between your system and our server.TCP connection setup latency : 29msThe time it takes your computer to set up a TCP connection with our server is 29 msec , which is good.Network bandwidth measurements : Upload 4.3 Mbit/sec , Download 7.1 Mbit/secYour Uplink : We measured your uplink 's sending bandwidth at 4.3 Mbit/sec .
This level of bandwidth works well for many users.Your Downlink : We measured your downlink 's receiving bandwidth at 7.1 Mbit/sec .
This level of bandwidth works well for many users.Network buffer measurements : Uplink 229 ms , Downlink 220 msWe estimate your uplink as having 230 msec of buffering .
This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.We estimate your</tokentext>
<sentencetext>My connection is comcast for biz-- go crazy- I took out my last subnetThe ICSI Netalyzr BetaIntroduction  Analysis  ResultsResult Summary74-92-106-XXX-Philadelphia.hfc.comcastbusiness.net / 74.92.106.XXXRecorded at 14:15 EDT (18:15 UTC) on Tue, June 09 2009.
Permalink. Transcript.Noteworthy EventsMinor AberrationsCertain protocols are blocked in outbound trafficAddress-based TestsNAT detection: NAT DetectedYour global IP address is 74.92.106.XXX while your local one is 192.168.15.XX.
You are behind a NAT.
Your local address is in unroutable address space.Your NAT renumbers TCP source ports sequentially.
The following graph shows connection attempts on the X-axis and their corresponding source ports on the Y-axis.DNS-based host information: OKYou are not a Tor exit node for HTTP traffic.You are not listed on any Spamhaus blacklists.The SORBS DUHL believes you are using a statically assigned IP address.Reachability TestsGeneral connectivity: NoteBasic UDP access is available.Direct UDP access to remote DNS servers (port 53) is allowed.The applet was also able to directly request a large DNS response.Direct UDP access to remote MSSQL servers (port 1434) is allowed.Direct TCP connections to remote FTP servers (port 21) failed.This is commonly due to how a NAT or firewall handles FTP traffic, as FTP causes unique problems when developing NATs and firewalls.Direct TCP access to remote SSH servers (port 22) is allowed.Direct TCP access to remote SMTP servers (port 25) is allowed.Direct TCP access to remote DNS servers (port 53) is allowed.Direct TCP access to remote HTTP servers (port 80) is allowed.Direct TCP access to remote POP servers (port 110) is allowed.Direct TCP access to remote RPC servers (port 135) is blocked.This is probably for security reasons, as this protocol is generally not designed for use outside the local network.Direct TCP access to remote NetBIOS servers (port 139) is blocked.This is probably for security reasons, as this protocol is generally not designed for use outside the local network.Direct TCP access to remote IMAP servers (port 143) is allowed.Direct TCP access to remote SNMP servers (port 161) is allowed.Direct TCP access to remote HTTPS servers (port 443) is allowed.Direct TCP access to remote SMB servers (port 445) is blocked.This is probably for security reasons, as this protocol is generally not designed for use outside the local network.Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.Direct TCP access to remote secure IMAP servers (port 585) is allowed.Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.Direct TCP access to remote POP/SSL servers (port 995) is allowed.Direct TCP access to remote SIP servers (port 5060) is allowed.Direct TCP access to remote BitTorrent servers (port 6881) is allowed.Network Access Link PropertiesNetwork latency measurements: Latency: 26ms Loss: 0.0\%The round-trip time (RTT) between your computer and our server is 26 msec, which is good.We recorded no packet loss between your system and our server.TCP connection setup latency: 29msThe time it takes your computer to set up a TCP connection with our server is 29 msec, which is good.Network bandwidth measurements: Upload 4.3 Mbit/sec, Download 7.1 Mbit/secYour Uplink: We measured your uplink's sending bandwidth at 4.3 Mbit/sec.
This level of bandwidth works well for many users.Your Downlink: We measured your downlink's receiving bandwidth at 7.1 Mbit/sec.
This level of bandwidth works well for many users.Network buffer measurements: Uplink 229 ms, Downlink 220 msWe estimate your uplink as having 230 msec of buffering.
This level may serve well for maximizing speed while minimizing the impact of large transfers on other traffic.We estimate your</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270427</id>
	<title>worse than hitler</title>
	<author>HappyEngineer</author>
	<datestamp>1244579940000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>I personally use the "worse than Hitler" meme all the time. When highway crews block a road and back up traffic I refer to them as worse than Hitler. When my landlord said I had to put my garbage can somewhere else I referred to him as worse than Hitler. My fiance has even sometimes jokingly said that I am worse than Hitler when I make some small infraction just because I use the phrase all the time.<br><br>I personally consider it an expression of emotion rather than a logical statement.</htmltext>
<tokenext>I personally use the " worse than Hitler " meme all the time .
When highway crews block a road and back up traffic I refer to them as worse than Hitler .
When my landlord said I had to put my garbage can somewhere else I referred to him as worse than Hitler .
My fiance has even sometimes jokingly said that I am worse than Hitler when I make some small infraction just because I use the phrase all the time.I personally consider it an expression of emotion rather than a logical statement .</tokentext>
<sentencetext>I personally use the "worse than Hitler" meme all the time.
When highway crews block a road and back up traffic I refer to them as worse than Hitler.
When my landlord said I had to put my garbage can somewhere else I referred to him as worse than Hitler.
My fiance has even sometimes jokingly said that I am worse than Hitler when I make some small infraction just because I use the phrase all the time.I personally consider it an expression of emotion rather than a logical statement.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269171</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270651</id>
	<title>Re:Not happening to me</title>
	<author>bsdaemonaut</author>
	<datestamp>1244580900000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>2</modscore>
	<htmltext><p>This really has nothing to do with dynamic/static IP's he's just trying to run his own private DNS server and it's getting hijacked. If he was seeking a simple dynamic IP solution it wouldn't matter if the client machine's DNS was getting hijacked since the DNS changes would get propagated out to Comcast's server eventually.</p><p>That being said this shouldn't effect him at all in a practicial sense. A private DNS server running inside of a private domain's network couldn't get hijacked except for when it has to seek upstream for an address it doesn't know, but for all practical uses this shouldn't matter. Your client machines would still be getting everything your DNS server is intentionally serving authoritatively or otherwise. The only time this would matter is if you want to completely ditch Comcast's DNS and go with another DNS server outside of your private domain, like OpenDNS.</p></htmltext>
<tokenext>This really has nothing to do with dynamic/static IP 's he 's just trying to run his own private DNS server and it 's getting hijacked .
If he was seeking a simple dynamic IP solution it would n't matter if the client machine 's DNS was getting hijacked since the DNS changes would get propagated out to Comcast 's server eventually.That being said this should n't effect him at all in a practicial sense .
A private DNS server running inside of a private domain 's network could n't get hijacked except for when it has to seek upstream for an address it does n't know , but for all practical uses this should n't matter .
Your client machines would still be getting everything your DNS server is intentionally serving authoritatively or otherwise .
The only time this would matter is if you want to completely ditch Comcast 's DNS and go with another DNS server outside of your private domain , like OpenDNS .</tokentext>
<sentencetext>This really has nothing to do with dynamic/static IP's he's just trying to run his own private DNS server and it's getting hijacked.
If he was seeking a simple dynamic IP solution it wouldn't matter if the client machine's DNS was getting hijacked since the DNS changes would get propagated out to Comcast's server eventually.That being said this shouldn't effect him at all in a practicial sense.
A private DNS server running inside of a private domain's network couldn't get hijacked except for when it has to seek upstream for an address it doesn't know, but for all practical uses this shouldn't matter.
Your client machines would still be getting everything your DNS server is intentionally serving authoritatively or otherwise.
The only time this would matter is if you want to completely ditch Comcast's DNS and go with another DNS server outside of your private domain, like OpenDNS.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269131</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269671</id>
	<title>Sorry Guys...</title>
	<author>Anonymous</author>
	<datestamp>1244576940000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Sorry guys, He's a hijacked machine on my botnet. I Apologize about the story.</p></htmltext>
<tokenext>Sorry guys , He 's a hijacked machine on my botnet .
I Apologize about the story .</tokentext>
<sentencetext>Sorry guys, He's a hijacked machine on my botnet.
I Apologize about the story.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273097</id>
	<title>Re:Fuck `Em All</title>
	<author>guyminuslife</author>
	<datestamp>1244550540000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>My immediate response to that is that you must be fucking half the Board of Directors, because that 2MB/sec? That's more than all of the rest of us (I no longer subscribe) get, in aggregate.</p></htmltext>
<tokenext>My immediate response to that is that you must be fucking half the Board of Directors , because that 2MB/sec ?
That 's more than all of the rest of us ( I no longer subscribe ) get , in aggregate .</tokentext>
<sentencetext>My immediate response to that is that you must be fucking half the Board of Directors, because that 2MB/sec?
That's more than all of the rest of us (I no longer subscribe) get, in aggregate.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270499</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269289</id>
	<title>Hmmm...</title>
	<author>tthomas48</author>
	<datestamp>1244575680000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>Interesting side-note. Time Warner's DNS servers stopped working recently for my Playstation 3. I switched to OpenDNS and all is well, but does anyone have an idea what's going on here? I thought DNS was DNS.</p></htmltext>
<tokenext>Interesting side-note .
Time Warner 's DNS servers stopped working recently for my Playstation 3 .
I switched to OpenDNS and all is well , but does anyone have an idea what 's going on here ?
I thought DNS was DNS .</tokentext>
<sentencetext>Interesting side-note.
Time Warner's DNS servers stopped working recently for my Playstation 3.
I switched to OpenDNS and all is well, but does anyone have an idea what's going on here?
I thought DNS was DNS.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269903</id>
	<title>Successful troll...</title>
	<author>Anonymous</author>
	<datestamp>1244578020000</datestamp>
	<modclass>Troll</modclass>
	<modscore>-1</modscore>
	<htmltext>is successful!</htmltext>
<tokenext>is successful !</tokentext>
<sentencetext>is successful!</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269821</id>
	<title>please remove links the the original article</title>
	<author>goffster</author>
	<datestamp>1244577600000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>It is simply wrong, misleading, and unworthy of slashdot</p></htmltext>
<tokenext>It is simply wrong , misleading , and unworthy of slashdot</tokentext>
<sentencetext>It is simply wrong, misleading, and unworthy of slashdot</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269215</id>
	<title>Re:Not happening to me</title>
	<author>Anonymous</author>
	<datestamp>1244575440000</datestamp>
	<modclass>Informativ</modclass>
	<modscore>3</modscore>
	<htmltext><blockquote><div><p>I just verified that it's not currently happening. I'm in California if that matters.</p></div></blockquote><p>

Me too. I'm also in CA and it is not curently happening.</p></div>
	</htmltext>
<tokenext>I just verified that it 's not currently happening .
I 'm in California if that matters .
Me too .
I 'm also in CA and it is not curently happening .</tokentext>
<sentencetext>I just verified that it's not currently happening.
I'm in California if that matters.
Me too.
I'm also in CA and it is not curently happening.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269431</id>
	<title>Re:Using OpenDNS here</title>
	<author>Anonymous</author>
	<datestamp>1244576040000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p><div class="quote"><p>I switched my DNS to OpenDNS because Comcast's DNS servers were unreliable for me. I am definitely hitting OpenDNS because if I typo a domain I'm redirected to the OpenDNS guide page. I'm a Northern California Comcast user.</p></div><p>Same here. Southern Maine user.</p></div>
	</htmltext>
<tokenext>I switched my DNS to OpenDNS because Comcast 's DNS servers were unreliable for me .
I am definitely hitting OpenDNS because if I typo a domain I 'm redirected to the OpenDNS guide page .
I 'm a Northern California Comcast user.Same here .
Southern Maine user .</tokentext>
<sentencetext>I switched my DNS to OpenDNS because Comcast's DNS servers were unreliable for me.
I am definitely hitting OpenDNS because if I typo a domain I'm redirected to the OpenDNS guide page.
I'm a Northern California Comcast user.Same here.
Southern Maine user.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269129</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272181</id>
	<title>reply</title>
	<author>snake pliskin</author>
	<datestamp>1244544660000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><a href="http://netalyzr.icsi.berkeley.edu/restore/id=43ca253f-12250-938258b8-71f4-4051-9c5a" title="berkeley.edu" rel="nofollow">http://netalyzr.icsi.berkeley.edu/restore/id=43ca253f-12250-938258b8-71f4-4051-9c5a</a> [berkeley.edu]</htmltext>
<tokenext>http : //netalyzr.icsi.berkeley.edu/restore/id = 43ca253f-12250-938258b8-71f4-4051-9c5a [ berkeley.edu ]</tokentext>
<sentencetext>http://netalyzr.icsi.berkeley.edu/restore/id=43ca253f-12250-938258b8-71f4-4051-9c5a [berkeley.edu]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271437</id>
	<title>ICSI Netalyzer results on comcast</title>
	<author>DragonTHC</author>
	<datestamp>1244541120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>DNS Tests</p><p>Restricted domain DNS lookup: OK<br>We are able to successfully lookup a name which resolves to the same IP address as our webserver. This means we are able to conduct many of the tests on your DNS server.</p><p>Unrestricted domain DNS lookup: OK<br>We are able to successfully lookup arbitrary names from within the Java applet. This means we are able to conduct all test on your DNS server.</p><p>DNS resolver address: OK<br>The IP address of your ISP's DNS Resolver is 68.87.74.164, which resolves to npls-cns02.bonitasprngs.fl.naples.comcast.net.</p><p>DNS resolver properties: Lookup latency: 130ms<br>Your ISP's DNS resolver requires 130 msec to conduct an external lookup.<br>Your resolver is using QTYPE=A for default queries.<br>Your resolver is not automatically performing IPv6 queries.<br>Your DNS resolver does not use EDNS.<br>Your resolver does not use 0x20 randomization, but will pass names in a case-sensitive manner.</p><p>DNS glue policy: OK<br>Your ISP's DNS resolver does not accept generic additional (glue) records -- good.<br>Your ISP's DNS resolver does not accept additional (glue) records which correspond to nameservers.<br>Your ISP's DNS resolver does not follow CNAMEs.</p><p>DNS resolver port randomization: OK<br>Your ISP's DNS resolver properly randomizes its local port number.<br>The following graph shows DNS requests on the x-axis and the detected source ports on the y-axis.</p><p>port sequence plot</p><p>DNS lookups of popular domains: OK<br>74 of 74 popular names were resolved successfully. Show all names.<br>In the following table reverse lookups that failed but for which a Start Of Authority (SOA) entry indicated correct name associations are shown using an "X", followed by the SOA entry. Absence of both IP address and reverse name indicates failed forward lookups.<br>Name     IP Address     Reverse Name/SOA<br>www.abbey.co.uk     165.160.13.20     X (pdns1.cscdns.net)<br>ad.doubleclick.net     74.125.242.24     iad09megaadvi[...]ubleclick.net<br>www.alliance-leicester.co.uk     194.130.105.121     X (alice.ioko365.com)<br>www.amazon.com     207.171.166.252     166-252.amazon.com<br>www.ameritrade.com     204.58.27.121     beta-new.tdameritrade.com<br>www.bankofamerica.com     171.161.161.173     www.bankofamerica.com<br>www.bankofscotland.co.uk     195.171.171.21     X (ns0.bt.net)<br>www.bankofthewest.com     207.114.194.101     X (dns1a.bankofthewest.com)<br>www.barclays.co.uk     213.219.1.141     X (dns1.lon7.telecityredbus.net)<br>www.capitalone.com     208.80.50.112     X (chia.arin.NET)<br>www.careerbuilder.com     208.82.7.22     X (smokey.careerbuilder.com)<br>www.chase.com     159.53.60.105     X (ns1.jpmorganchase.com)<br>chaseonline.chase.com     159.53.64.54     resources-cdc2.chase.com<br>www.citi.com     192.193.232.227     X (ns.citicorp.com)<br>www.citibank.com     192.193.232.227     X (ns.citicorp.com)<br>www.citimortgage.com     192.193.103.118     X (ns.citicorp.com)<br>www.cnn.com     157.166.226.26     www.cnn.com<br>www.desjardins.com     142.195.128.44     desjardins.com<br>www.deutsche-bank.de     217.73.49.24     www.deutsche-bank.de<br>www.e-gold.com     209.200.169.10     unknown.prolexic.com<br>www.ebay.com     66.135.217.243     hp-core.ebay.com<br>www.etrade.com     12.153.224.22     etrade.com<br>www.f-secure.com     96.17.147.114     a96-17-147-114.[...]echnologies.com<br>www.facebook.com     69.63.186.31     www.13.06.ash1.facebook.com<br>www.fdic.gov     192.147.69.84     www.fdic.gov<br>www.friendfinder.com     208.88.180.81     X (ii53-30.friendfinderinc.com)<br>www.geocities.com     98.137.46.72     intl1.geo.vip.sp2.yahoo.com<br>www.google.com     74.125.65.103     gx-in-f103.google.com<br>www.halifax.co.uk     212.140.245.97     halifax.co.uk<br>www.hsbc.co.uk     193.108.74.126     X (ns3.hsbc.com)<br>www.irs.gov     96.17.147.97     a96-17-147-97.d[...]echnologies.com<br>www.jpmorganchase.com     159.53.60.166     X (ns1.jpmorganchase.com)<br>www.lloydstsb.com     193.34.230.181     X (ns2.lloydstsb.co.uk)<br>mail.google.com     209.85.133</p></htmltext>
<tokenext>DNS TestsRestricted domain DNS lookup : OKWe are able to successfully lookup a name which resolves to the same IP address as our webserver .
This means we are able to conduct many of the tests on your DNS server.Unrestricted domain DNS lookup : OKWe are able to successfully lookup arbitrary names from within the Java applet .
This means we are able to conduct all test on your DNS server.DNS resolver address : OKThe IP address of your ISP 's DNS Resolver is 68.87.74.164 , which resolves to npls-cns02.bonitasprngs.fl.naples.comcast.net.DNS resolver properties : Lookup latency : 130msYour ISP 's DNS resolver requires 130 msec to conduct an external lookup.Your resolver is using QTYPE = A for default queries.Your resolver is not automatically performing IPv6 queries.Your DNS resolver does not use EDNS.Your resolver does not use 0x20 randomization , but will pass names in a case-sensitive manner.DNS glue policy : OKYour ISP 's DNS resolver does not accept generic additional ( glue ) records -- good.Your ISP 's DNS resolver does not accept additional ( glue ) records which correspond to nameservers.Your ISP 's DNS resolver does not follow CNAMEs.DNS resolver port randomization : OKYour ISP 's DNS resolver properly randomizes its local port number.The following graph shows DNS requests on the x-axis and the detected source ports on the y-axis.port sequence plotDNS lookups of popular domains : OK74 of 74 popular names were resolved successfully .
Show all names.In the following table reverse lookups that failed but for which a Start Of Authority ( SOA ) entry indicated correct name associations are shown using an " X " , followed by the SOA entry .
Absence of both IP address and reverse name indicates failed forward lookups.Name IP Address Reverse Name/SOAwww.abbey.co.uk 165.160.13.20 X ( pdns1.cscdns.net ) ad.doubleclick.net 74.125.242.24 iad09megaadvi [ ... ] ubleclick.netwww.alliance-leicester.co.uk 194.130.105.121 X ( alice.ioko365.com ) www.amazon.com 207.171.166.252 166-252.amazon.comwww.ameritrade.com 204.58.27.121 beta-new.tdameritrade.comwww.bankofamerica.com 171.161.161.173 www.bankofamerica.comwww.bankofscotland.co.uk 195.171.171.21 X ( ns0.bt.net ) www.bankofthewest.com 207.114.194.101 X ( dns1a.bankofthewest.com ) www.barclays.co.uk 213.219.1.141 X ( dns1.lon7.telecityredbus.net ) www.capitalone.com 208.80.50.112 X ( chia.arin.NET ) www.careerbuilder.com 208.82.7.22 X ( smokey.careerbuilder.com ) www.chase.com 159.53.60.105 X ( ns1.jpmorganchase.com ) chaseonline.chase.com 159.53.64.54 resources-cdc2.chase.comwww.citi.com 192.193.232.227 X ( ns.citicorp.com ) www.citibank.com 192.193.232.227 X ( ns.citicorp.com ) www.citimortgage.com 192.193.103.118 X ( ns.citicorp.com ) www.cnn.com 157.166.226.26 www.cnn.comwww.desjardins.com 142.195.128.44 desjardins.comwww.deutsche-bank.de 217.73.49.24 www.deutsche-bank.dewww.e-gold.com 209.200.169.10 unknown.prolexic.comwww.ebay.com 66.135.217.243 hp-core.ebay.comwww.etrade.com 12.153.224.22 etrade.comwww.f-secure.com 96.17.147.114 a96-17-147-114. [ .. .
] echnologies.comwww.facebook.com 69.63.186.31 www.13.06.ash1.facebook.comwww.fdic.gov 192.147.69.84 www.fdic.govwww.friendfinder.com 208.88.180.81 X ( ii53-30.friendfinderinc.com ) www.geocities.com 98.137.46.72 intl1.geo.vip.sp2.yahoo.comwww.google.com 74.125.65.103 gx-in-f103.google.comwww.halifax.co.uk 212.140.245.97 halifax.co.ukwww.hsbc.co.uk 193.108.74.126 X ( ns3.hsbc.com ) www.irs.gov 96.17.147.97 a96-17-147-97.d [ ... ] echnologies.comwww.jpmorganchase.com 159.53.60.166 X ( ns1.jpmorganchase.com ) www.lloydstsb.com 193.34.230.181 X ( ns2.lloydstsb.co.uk ) mail.google.com 209.85.133</tokentext>
<sentencetext>DNS TestsRestricted domain DNS lookup: OKWe are able to successfully lookup a name which resolves to the same IP address as our webserver.
This means we are able to conduct many of the tests on your DNS server.Unrestricted domain DNS lookup: OKWe are able to successfully lookup arbitrary names from within the Java applet.
This means we are able to conduct all test on your DNS server.DNS resolver address: OKThe IP address of your ISP's DNS Resolver is 68.87.74.164, which resolves to npls-cns02.bonitasprngs.fl.naples.comcast.net.DNS resolver properties: Lookup latency: 130msYour ISP's DNS resolver requires 130 msec to conduct an external lookup.Your resolver is using QTYPE=A for default queries.Your resolver is not automatically performing IPv6 queries.Your DNS resolver does not use EDNS.Your resolver does not use 0x20 randomization, but will pass names in a case-sensitive manner.DNS glue policy: OKYour ISP's DNS resolver does not accept generic additional (glue) records -- good.Your ISP's DNS resolver does not accept additional (glue) records which correspond to nameservers.Your ISP's DNS resolver does not follow CNAMEs.DNS resolver port randomization: OKYour ISP's DNS resolver properly randomizes its local port number.The following graph shows DNS requests on the x-axis and the detected source ports on the y-axis.port sequence plotDNS lookups of popular domains: OK74 of 74 popular names were resolved successfully.
Show all names.In the following table reverse lookups that failed but for which a Start Of Authority (SOA) entry indicated correct name associations are shown using an "X", followed by the SOA entry.
Absence of both IP address and reverse name indicates failed forward lookups.Name     IP Address     Reverse Name/SOAwww.abbey.co.uk     165.160.13.20     X (pdns1.cscdns.net)ad.doubleclick.net     74.125.242.24     iad09megaadvi[...]ubleclick.netwww.alliance-leicester.co.uk     194.130.105.121     X (alice.ioko365.com)www.amazon.com     207.171.166.252     166-252.amazon.comwww.ameritrade.com     204.58.27.121     beta-new.tdameritrade.comwww.bankofamerica.com     171.161.161.173     www.bankofamerica.comwww.bankofscotland.co.uk     195.171.171.21     X (ns0.bt.net)www.bankofthewest.com     207.114.194.101     X (dns1a.bankofthewest.com)www.barclays.co.uk     213.219.1.141     X (dns1.lon7.telecityredbus.net)www.capitalone.com     208.80.50.112     X (chia.arin.NET)www.careerbuilder.com     208.82.7.22     X (smokey.careerbuilder.com)www.chase.com     159.53.60.105     X (ns1.jpmorganchase.com)chaseonline.chase.com     159.53.64.54     resources-cdc2.chase.comwww.citi.com     192.193.232.227     X (ns.citicorp.com)www.citibank.com     192.193.232.227     X (ns.citicorp.com)www.citimortgage.com     192.193.103.118     X (ns.citicorp.com)www.cnn.com     157.166.226.26     www.cnn.comwww.desjardins.com     142.195.128.44     desjardins.comwww.deutsche-bank.de     217.73.49.24     www.deutsche-bank.dewww.e-gold.com     209.200.169.10     unknown.prolexic.comwww.ebay.com     66.135.217.243     hp-core.ebay.comwww.etrade.com     12.153.224.22     etrade.comwww.f-secure.com     96.17.147.114     a96-17-147-114.[...
]echnologies.comwww.facebook.com     69.63.186.31     www.13.06.ash1.facebook.comwww.fdic.gov     192.147.69.84     www.fdic.govwww.friendfinder.com     208.88.180.81     X (ii53-30.friendfinderinc.com)www.geocities.com     98.137.46.72     intl1.geo.vip.sp2.yahoo.comwww.google.com     74.125.65.103     gx-in-f103.google.comwww.halifax.co.uk     212.140.245.97     halifax.co.ukwww.hsbc.co.uk     193.108.74.126     X (ns3.hsbc.com)www.irs.gov     96.17.147.97     a96-17-147-97.d[...]echnologies.comwww.jpmorganchase.com     159.53.60.166     X (ns1.jpmorganchase.com)www.lloydstsb.com     193.34.230.181     X (ns2.lloydstsb.co.uk)mail.google.com     209.85.133</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28292073</id>
	<title>Re:Static Dynamic IPs</title>
	<author>ohnobinki</author>
	<datestamp>1244729100000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p><div class="quote"><p>Are you running that and hoping that your dynamic IP address doesn't change or do you have a business account with a fixed IP?  If it's a business account than I would assume that they aren't redirecting those but could still be redirecting on consumer accounts.</p></div><p>
Dynamic IPs are not ``dynamic'' if one nevers gives up the lease. I have WOW (wide open west / <a href="http://wowway.com/" title="wowway.com" rel="nofollow">http://wowway.com/</a> [wowway.com] ) Internet and the only time my IP has changed is when our router was replaced (giving it a different client ID) and, of course, when I directly plugged my computer into a hub connected to the modem (to give it direct Internet access). Because WOW has blocked all UDP traffic on port 53, I have a gracious friend who has ComCast and serves my DNS. Comcast doesn't seem to change IPs unless if the router/DHCP client releases a lease. This means I essentially don't need to change glue records at all. But Comcast has seemed to more often supposedly required people to re-plug-in their modems and (I'm guessing only from slight experience) Comcast may have even forced an IP change upon one router I've had access to.</p><p>Has any other WOW user tested serving DNS? I sent a query to WOW people and they said:</p><p><div class="quote"><p>Port 53 is reserved for internal WOW! network use
only. Please try using an alternate port.</p></div></div>
	</htmltext>
<tokenext>Are you running that and hoping that your dynamic IP address does n't change or do you have a business account with a fixed IP ?
If it 's a business account than I would assume that they are n't redirecting those but could still be redirecting on consumer accounts .
Dynamic IPs are not ` ` dynamic' ' if one nevers gives up the lease .
I have WOW ( wide open west / http : //wowway.com/ [ wowway.com ] ) Internet and the only time my IP has changed is when our router was replaced ( giving it a different client ID ) and , of course , when I directly plugged my computer into a hub connected to the modem ( to give it direct Internet access ) .
Because WOW has blocked all UDP traffic on port 53 , I have a gracious friend who has ComCast and serves my DNS .
Comcast does n't seem to change IPs unless if the router/DHCP client releases a lease .
This means I essentially do n't need to change glue records at all .
But Comcast has seemed to more often supposedly required people to re-plug-in their modems and ( I 'm guessing only from slight experience ) Comcast may have even forced an IP change upon one router I 've had access to.Has any other WOW user tested serving DNS ?
I sent a query to WOW people and they said : Port 53 is reserved for internal WOW !
network use only .
Please try using an alternate port .</tokentext>
<sentencetext>Are you running that and hoping that your dynamic IP address doesn't change or do you have a business account with a fixed IP?
If it's a business account than I would assume that they aren't redirecting those but could still be redirecting on consumer accounts.
Dynamic IPs are not ``dynamic'' if one nevers gives up the lease.
I have WOW (wide open west / http://wowway.com/ [wowway.com] ) Internet and the only time my IP has changed is when our router was replaced (giving it a different client ID) and, of course, when I directly plugged my computer into a hub connected to the modem (to give it direct Internet access).
Because WOW has blocked all UDP traffic on port 53, I have a gracious friend who has ComCast and serves my DNS.
Comcast doesn't seem to change IPs unless if the router/DHCP client releases a lease.
This means I essentially don't need to change glue records at all.
But Comcast has seemed to more often supposedly required people to re-plug-in their modems and (I'm guessing only from slight experience) Comcast may have even forced an IP change upon one router I've had access to.Has any other WOW user tested serving DNS?
I sent a query to WOW people and they said:Port 53 is reserved for internal WOW!
network use
only.
Please try using an alternate port.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269131</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269441</id>
	<title>Falsely advertising "Internet access"</title>
	<author>davidwr</author>
	<datestamp>1244576040000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Are you buying "Internet access" or something else?  If you bought "Internet access" and you aren't getting it that's breach of contract.  Odds are you are buying "partial Internet access as spelled out by the terms and conditions" which is probably not "Internet access."</p><p>Are they advertising "Internet access" or something else?  If they are advertising "Internet access" and not delivering, that's false advertising.  Unfortunately, it takes either deep pockets or a friend in your friendly neighborhood Attorney General's office to fight this battle.</p><p>Of course, most major IPSs haven't delivered "Internet access" to home users for years.  They routinely block port 25 and other widely-abused ports, and some throttle traffic in ways that are not non-discriminatory.  Business users, especially big business users, usually can get real Internet access but they have to pay.</p></htmltext>
<tokenext>Are you buying " Internet access " or something else ?
If you bought " Internet access " and you are n't getting it that 's breach of contract .
Odds are you are buying " partial Internet access as spelled out by the terms and conditions " which is probably not " Internet access .
" Are they advertising " Internet access " or something else ?
If they are advertising " Internet access " and not delivering , that 's false advertising .
Unfortunately , it takes either deep pockets or a friend in your friendly neighborhood Attorney General 's office to fight this battle.Of course , most major IPSs have n't delivered " Internet access " to home users for years .
They routinely block port 25 and other widely-abused ports , and some throttle traffic in ways that are not non-discriminatory .
Business users , especially big business users , usually can get real Internet access but they have to pay .</tokentext>
<sentencetext>Are you buying "Internet access" or something else?
If you bought "Internet access" and you aren't getting it that's breach of contract.
Odds are you are buying "partial Internet access as spelled out by the terms and conditions" which is probably not "Internet access.
"Are they advertising "Internet access" or something else?
If they are advertising "Internet access" and not delivering, that's false advertising.
Unfortunately, it takes either deep pockets or a friend in your friendly neighborhood Attorney General's office to fight this battle.Of course, most major IPSs haven't delivered "Internet access" to home users for years.
They routinely block port 25 and other widely-abused ports, and some throttle traffic in ways that are not non-discriminatory.
Business users, especially big business users, usually can get real Internet access but they have to pay.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269755</id>
	<title>Re:So let me see if I have this straight...</title>
	<author>Alzheimers</author>
	<datestamp>1244577360000</datestamp>
	<modclass>Insightful</modclass>
	<modscore>4</modscore>
	<htmltext><p>Welcome to the new Media Democracy.</p></htmltext>
<tokenext>Welcome to the new Media Democracy .</tokentext>
<sentencetext>Welcome to the new Media Democracy.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269573</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270491</id>
	<title>My /etc/hosts is REALLY long</title>
	<author>Anonymous</author>
	<datestamp>1244580180000</datestamp>
	<modclass>Funny</modclass>
	<modscore>1</modscore>
	<htmltext><p>I don't trust DNS.</p><p>My<nobr> <wbr></nobr>/etc/hosts is REEEEEEEEEEEEEEAAAAAAAAAAAALLLLLLLLLLLLLLLLY long.</p><p>Every once in a while, a site doesn't work anymore.<br>When that happens, I call my parents to get the new IP address.</p></htmltext>
<tokenext>I do n't trust DNS.My /etc/hosts is REEEEEEEEEEEEEEAAAAAAAAAAAALLLLLLLLLLLLLLLLY long.Every once in a while , a site does n't work anymore.When that happens , I call my parents to get the new IP address .</tokentext>
<sentencetext>I don't trust DNS.My /etc/hosts is REEEEEEEEEEEEEEAAAAAAAAAAAALLLLLLLLLLLLLLLLY long.Every once in a while, a site doesn't work anymore.When that happens, I call my parents to get the new IP address.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273581</id>
	<title>Re:So let me see if I have this straight...</title>
	<author>Anonymous</author>
	<datestamp>1244554080000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>Hey, slow news day.</p></htmltext>
<tokenext>Hey , slow news day .</tokentext>
<sentencetext>Hey, slow news day.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269573</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272655</id>
	<title>Lake County, IL</title>
	<author>Anonymous</author>
	<datestamp>1244547660000</datestamp>
	<modclass>None</modclass>
	<modscore>0</modscore>
	<htmltext><p>This is what I have. I figure the service is about the same for a whole bunch of small cities just north of Chicago, so I'm putting down the county rather than the specific city for my location. (Also I think most of the stuff that is blocked is due to my router settings. I don't see a reason to have ports open if I'm not actively using them.)</p><p><b>Reachability Tests:</b><br>General connectivity: Note<br>Basic UDP access is available.<br>Direct UDP access to remote DNS servers (port 53) is allowed.<br>The applet was also able to directly request a large DNS response.<br>Direct UDP access to remote MSSQL servers (port 1434) is allowed.<br>Direct TCP connections to remote FTP servers (port 21) failed.<br>This is commonly due to how a NAT or firewall handles FTP traffic, as FTP causes unique problems when developing NATs and firewalls.<br>Direct TCP access to remote SSH servers (port 22) is allowed.<br>Direct TCP access to remote SMTP servers (port 25) is allowed.<br>Direct TCP access to remote DNS servers (port 53) is allowed.<br>Direct TCP access to remote HTTP servers (port 80) is allowed.<br>Direct TCP access to remote POP servers (port 110) is allowed.<br>Direct TCP access to remote RPC servers (port 135) is blocked.<br>This is probably for security reasons, as this protocol is generally not designed for use outside the local network.<br>Direct TCP access to remote NetBIOS servers (port 139) is blocked.<br>This is probably for security reasons, as this protocol is generally not designed for use outside the local network.<br>Direct TCP access to remote IMAP servers (port 143) is allowed.<br>Direct TCP access to remote SNMP servers (port 161) is allowed.<br>Direct TCP access to remote HTTPS servers (port 443) is allowed.<br>Direct TCP access to remote SMB servers (port 445) is blocked.<br>This is probably for security reasons, as this protocol is generally not designed for use outside the local network.<br>Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.<br>Direct TCP access to remote secure IMAP servers (port 585) is allowed.<br>Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.<br>Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.<br>Direct TCP access to remote POP/SSL servers (port 995) is allowed.<br>Direct TCP access to remote SIP servers (port 5060) is allowed.<br>Direct TCP access to remote BitTorrent servers (port 6881) is allowed.</p></htmltext>
<tokenext>This is what I have .
I figure the service is about the same for a whole bunch of small cities just north of Chicago , so I 'm putting down the county rather than the specific city for my location .
( Also I think most of the stuff that is blocked is due to my router settings .
I do n't see a reason to have ports open if I 'm not actively using them .
) Reachability Tests : General connectivity : NoteBasic UDP access is available.Direct UDP access to remote DNS servers ( port 53 ) is allowed.The applet was also able to directly request a large DNS response.Direct UDP access to remote MSSQL servers ( port 1434 ) is allowed.Direct TCP connections to remote FTP servers ( port 21 ) failed.This is commonly due to how a NAT or firewall handles FTP traffic , as FTP causes unique problems when developing NATs and firewalls.Direct TCP access to remote SSH servers ( port 22 ) is allowed.Direct TCP access to remote SMTP servers ( port 25 ) is allowed.Direct TCP access to remote DNS servers ( port 53 ) is allowed.Direct TCP access to remote HTTP servers ( port 80 ) is allowed.Direct TCP access to remote POP servers ( port 110 ) is allowed.Direct TCP access to remote RPC servers ( port 135 ) is blocked.This is probably for security reasons , as this protocol is generally not designed for use outside the local network.Direct TCP access to remote NetBIOS servers ( port 139 ) is blocked.This is probably for security reasons , as this protocol is generally not designed for use outside the local network.Direct TCP access to remote IMAP servers ( port 143 ) is allowed.Direct TCP access to remote SNMP servers ( port 161 ) is allowed.Direct TCP access to remote HTTPS servers ( port 443 ) is allowed.Direct TCP access to remote SMB servers ( port 445 ) is blocked.This is probably for security reasons , as this protocol is generally not designed for use outside the local network.Direct TCP access to remote SMTP/SSL servers ( port 465 ) is allowed.Direct TCP access to remote secure IMAP servers ( port 585 ) is allowed.Direct TCP access to remote authenticated SMTP servers ( port 587 ) is allowed.Direct TCP access to remote IMAP/SSL servers ( port 993 ) is allowed.Direct TCP access to remote POP/SSL servers ( port 995 ) is allowed.Direct TCP access to remote SIP servers ( port 5060 ) is allowed.Direct TCP access to remote BitTorrent servers ( port 6881 ) is allowed .</tokentext>
<sentencetext>This is what I have.
I figure the service is about the same for a whole bunch of small cities just north of Chicago, so I'm putting down the county rather than the specific city for my location.
(Also I think most of the stuff that is blocked is due to my router settings.
I don't see a reason to have ports open if I'm not actively using them.
)Reachability Tests:General connectivity: NoteBasic UDP access is available.Direct UDP access to remote DNS servers (port 53) is allowed.The applet was also able to directly request a large DNS response.Direct UDP access to remote MSSQL servers (port 1434) is allowed.Direct TCP connections to remote FTP servers (port 21) failed.This is commonly due to how a NAT or firewall handles FTP traffic, as FTP causes unique problems when developing NATs and firewalls.Direct TCP access to remote SSH servers (port 22) is allowed.Direct TCP access to remote SMTP servers (port 25) is allowed.Direct TCP access to remote DNS servers (port 53) is allowed.Direct TCP access to remote HTTP servers (port 80) is allowed.Direct TCP access to remote POP servers (port 110) is allowed.Direct TCP access to remote RPC servers (port 135) is blocked.This is probably for security reasons, as this protocol is generally not designed for use outside the local network.Direct TCP access to remote NetBIOS servers (port 139) is blocked.This is probably for security reasons, as this protocol is generally not designed for use outside the local network.Direct TCP access to remote IMAP servers (port 143) is allowed.Direct TCP access to remote SNMP servers (port 161) is allowed.Direct TCP access to remote HTTPS servers (port 443) is allowed.Direct TCP access to remote SMB servers (port 445) is blocked.This is probably for security reasons, as this protocol is generally not designed for use outside the local network.Direct TCP access to remote SMTP/SSL servers (port 465) is allowed.Direct TCP access to remote secure IMAP servers (port 585) is allowed.Direct TCP access to remote authenticated SMTP servers (port 587) is allowed.Direct TCP access to remote IMAP/SSL servers (port 993) is allowed.Direct TCP access to remote POP/SSL servers (port 995) is allowed.Direct TCP access to remote SIP servers (port 5060) is allowed.Direct TCP access to remote BitTorrent servers (port 6881) is allowed.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270615</id>
	<title>Re:As one of the authors of Netalyzr...</title>
	<author>msimm</author>
	<datestamp>1244580720000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Thanks, great project.</htmltext>
<tokenext>Thanks , great project .</tokentext>
<sentencetext>Thanks, great project.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269563</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269131</id>
	<title>Re:Not happening to me</title>
	<author>Anonymous</author>
	<datestamp>1244575200000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>5</modscore>
	<htmltext><p><div class="quote"><p>I'm a Comcast user, and I run a DNS server for a few private domains that only I use</p></div><p>Are you running that and hoping that your dynamic IP address doesn't change or do you have a business account with a fixed IP?  If it's a business account than I would assume that they aren't redirecting those but could still be redirecting on consumer accounts.</p></div>
	</htmltext>
<tokenext>I 'm a Comcast user , and I run a DNS server for a few private domains that only I useAre you running that and hoping that your dynamic IP address does n't change or do you have a business account with a fixed IP ?
If it 's a business account than I would assume that they are n't redirecting those but could still be redirecting on consumer accounts .</tokentext>
<sentencetext>I'm a Comcast user, and I run a DNS server for a few private domains that only I useAre you running that and hoping that your dynamic IP address doesn't change or do you have a business account with a fixed IP?
If it's a business account than I would assume that they aren't redirecting those but could still be redirecting on consumer accounts.
	</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271219</id>
	<title>How to get around it</title>
	<author>rs79</author>
	<datestamp>1244540160000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>So primary the root zone for yourself and don't use their DNS. They can't intercept DNS requests to 127.0.0.1</p><p>The root zone is just a bunch of pointers to the TLD servers that have all the big files and the root zone is tiny.</p><p>Just declare yourself authoritative for . and use the root zone of your choice. The legacy one is at : <a href="ftp://rs.internic.net/domain/" title="internic.net">ftp://rs.internic.net/domain/</a> [internic.net]</p></htmltext>
<tokenext>So primary the root zone for yourself and do n't use their DNS .
They ca n't intercept DNS requests to 127.0.0.1The root zone is just a bunch of pointers to the TLD servers that have all the big files and the root zone is tiny.Just declare yourself authoritative for .
and use the root zone of your choice .
The legacy one is at : ftp : //rs.internic.net/domain/ [ internic.net ]</tokentext>
<sentencetext>So primary the root zone for yourself and don't use their DNS.
They can't intercept DNS requests to 127.0.0.1The root zone is just a bunch of pointers to the TLD servers that have all the big files and the root zone is tiny.Just declare yourself authoritative for .
and use the root zone of your choice.
The legacy one is at : ftp://rs.internic.net/domain/ [internic.net]</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269385</id>
	<title>Comcast results in PA.</title>
	<author>thesolo</author>
	<datestamp>1244575920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><a href="http://n7.netalyzr.icsi.berkeley.edu/summary/id=ae8199f5-18744-558513c5-8687-417b-a9f5" title="berkeley.edu">Here are my ICSI results</a> [berkeley.edu].
<br> <br>
Direct UDP access to remote DNS servers (port 53) is allowed.<br>
Direct TCP access to remote DNS servers (port 53) is allowed.<br>
<br> <br>
My office is just outside of Philadelphia, so southeastern PA, for regional results.</htmltext>
<tokenext>Here are my ICSI results [ berkeley.edu ] .
Direct UDP access to remote DNS servers ( port 53 ) is allowed .
Direct TCP access to remote DNS servers ( port 53 ) is allowed .
My office is just outside of Philadelphia , so southeastern PA , for regional results .</tokentext>
<sentencetext>Here are my ICSI results [berkeley.edu].
Direct UDP access to remote DNS servers (port 53) is allowed.
Direct TCP access to remote DNS servers (port 53) is allowed.
My office is just outside of Philadelphia, so southeastern PA, for regional results.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269293</id>
	<title>NN wars?</title>
	<author>Red Flayer</author>
	<datestamp>1244575740000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><blockquote><div><p>If true, this is a pretty serious escalation in the Net Neutrality wars.</p><blockquote><div><p>It's not just an escalation in the NN wars (I didn't know we were fighting a war, anyway.  I thought it was just a 'security detachment' or 'police action').<br> <br>This represents a fundamental shift in how the internet works.  If you can't use your own DNS servers, or at least send requests to an outside DNS server, then the internet loses some of its ability to route around damage (again, using the convention that 'damage' includes shit like deep packet inspection, etc).<br> <br>If true, this is really a sad day... for it represents the true beginning of the end of the internet as we know it.<br> <br>And now that I've got the Chicken Little hyperbole out of the way... seems to me like Comcast wants to be a forced portal, not just an ISP.  Hopefully they are rewarded with the same fate AOL was rewarded.</p></div></blockquote></div></blockquote></div>
	</htmltext>
<tokenext>If true , this is a pretty serious escalation in the Net Neutrality wars.It 's not just an escalation in the NN wars ( I did n't know we were fighting a war , anyway .
I thought it was just a 'security detachment ' or 'police action ' ) .
This represents a fundamental shift in how the internet works .
If you ca n't use your own DNS servers , or at least send requests to an outside DNS server , then the internet loses some of its ability to route around damage ( again , using the convention that 'damage ' includes shit like deep packet inspection , etc ) .
If true , this is really a sad day... for it represents the true beginning of the end of the internet as we know it .
And now that I 've got the Chicken Little hyperbole out of the way... seems to me like Comcast wants to be a forced portal , not just an ISP .
Hopefully they are rewarded with the same fate AOL was rewarded .</tokentext>
<sentencetext>If true, this is a pretty serious escalation in the Net Neutrality wars.It's not just an escalation in the NN wars (I didn't know we were fighting a war, anyway.
I thought it was just a 'security detachment' or 'police action').
This represents a fundamental shift in how the internet works.
If you can't use your own DNS servers, or at least send requests to an outside DNS server, then the internet loses some of its ability to route around damage (again, using the convention that 'damage' includes shit like deep packet inspection, etc).
If true, this is really a sad day... for it represents the true beginning of the end of the internet as we know it.
And now that I've got the Chicken Little hyperbole out of the way... seems to me like Comcast wants to be a forced portal, not just an ISP.
Hopefully they are rewarded with the same fate AOL was rewarded.
	</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272847</id>
	<title>Re:"Official Response"</title>
	<author>wolrahnaes</author>
	<datestamp>1244548920000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>As many things as there are to legitimately bitch about when it comes to Comcast, they were one of the pioneering companies in responding directly and publicly to complaints raised via the Internet.  I don't know how long it will last, whether this is a fad or a lasting trend, but regardless of how it ends up working out I have to give them that it's great PR and seems to be working well at the moment.</p></htmltext>
<tokenext>As many things as there are to legitimately bitch about when it comes to Comcast , they were one of the pioneering companies in responding directly and publicly to complaints raised via the Internet .
I do n't know how long it will last , whether this is a fad or a lasting trend , but regardless of how it ends up working out I have to give them that it 's great PR and seems to be working well at the moment .</tokentext>
<sentencetext>As many things as there are to legitimately bitch about when it comes to Comcast, they were one of the pioneering companies in responding directly and publicly to complaints raised via the Internet.
I don't know how long it will last, whether this is a fad or a lasting trend, but regardless of how it ends up working out I have to give them that it's great PR and seems to be working well at the moment.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270179</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272265</id>
	<title>Wouldn't mind so much</title>
	<author>OrangeTide</author>
	<datestamp>1244545080000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>I wouldn't mind so much if comcast's DNS servers didn't break on a regular basis. I use a different DNS because I got sick of waiting for theirs to come back up during some stupid 1am maintenance schedule. Why can't they do the maintenance at noon when housewives are on and hackers are sleeping?</p></htmltext>
<tokenext>I would n't mind so much if comcast 's DNS servers did n't break on a regular basis .
I use a different DNS because I got sick of waiting for theirs to come back up during some stupid 1am maintenance schedule .
Why ca n't they do the maintenance at noon when housewives are on and hackers are sleeping ?</tokentext>
<sentencetext>I wouldn't mind so much if comcast's DNS servers didn't break on a regular basis.
I use a different DNS because I got sick of waiting for theirs to come back up during some stupid 1am maintenance schedule.
Why can't they do the maintenance at noon when housewives are on and hackers are sleeping?</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269945</id>
	<title>Re:So let me see if I have this straight...</title>
	<author>Anonymous</author>
	<datestamp>1244578200000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><p>You must be new here.</p></htmltext>
<tokenext>You must be new here .</tokentext>
<sentencetext>You must be new here.</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269573</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269313</id>
	<title>Works fine in Chicago too</title>
	<author>hoosbane</author>
	<datestamp>1244575800000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>Just tried it from my home machine on Comcast in Chicago, and nothing's being redirected.  Lookups for non-existant domains return NXDOMAIN like they should.</htmltext>
<tokenext>Just tried it from my home machine on Comcast in Chicago , and nothing 's being redirected .
Lookups for non-existant domains return NXDOMAIN like they should .</tokentext>
<sentencetext>Just tried it from my home machine on Comcast in Chicago, and nothing's being redirected.
Lookups for non-existant domains return NXDOMAIN like they should.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272601</id>
	<title>Re:As one of the authors of Netalyzr...</title>
	<author>wren337</author>
	<datestamp>1244547360000</datestamp>
	<modclass>Interestin</modclass>
	<modscore>2</modscore>
	<htmltext><p>Looks like wowway is hijacking www.google.com, capturing the search and then doing a 302 to the actual search page (?)</p><p><a href="http://netalyzr.icsi.berkeley.edu/restore/id=4b65aebb-24385-1985f52c-c397-4cc4-b780" title="berkeley.edu">http://netalyzr.icsi.berkeley.edu/restore/id=4b65aebb-24385-1985f52c-c397-4cc4-b780</a> [berkeley.edu]</p></htmltext>
<tokenext>Looks like wowway is hijacking www.google.com , capturing the search and then doing a 302 to the actual search page ( ?
) http : //netalyzr.icsi.berkeley.edu/restore/id = 4b65aebb-24385-1985f52c-c397-4cc4-b780 [ berkeley.edu ]</tokentext>
<sentencetext>Looks like wowway is hijacking www.google.com, capturing the search and then doing a 302 to the actual search page (?
)http://netalyzr.icsi.berkeley.edu/restore/id=4b65aebb-24385-1985f52c-c397-4cc4-b780 [berkeley.edu]</sentencetext>
	<parent>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269563</parent>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273041</id>
	<title>Does not seem correct. For me at least.</title>
	<author>Tjp($)pjT</author>
	<datestamp>1244550120000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext><tt>
$ nslookup<br>
&gt; server 207.69.131.9<br>
Default server: 207.69.131.9<br>
Address: 207.69.131.9#53<br>
&gt; comcast.sucks.com<br><nobr> <wbr></nobr>;; connection timed out; no servers could be reached<br>
&gt; server www.microsoft.com<br>
Default server: www.microsoft.com<br>
Address: 207.46.193.254#53<br>
Default server: www.microsoft.com<br>
Address: 207.46.192.254#53<br>
&gt; comcast.sucks.com<br><nobr> <wbr></nobr>;; connection timed out; no servers could be reached<br>
&gt; <br>
</tt>
<br>So when I point lookups at the comcast ad servers even, or Microsoft, the lookups fail. Might be because we are on a business account here (to get a block of static IPs) but if our own captive ISP DNS servers are not reachable we'd have problems as we have some internal non-standard stuff going on for our internal networking. Our faked top level domain for our non-routable machines just would not show up. Again, might be because we are business clients of Comcast, but they have done all sorts of things like capped our bandwidth, excessively applied traffic shaping, etc. (corrected with a phone call mentioning we are business clients and \_they\_ committed to the usage rates we subscribed to.) But other than a few glitches we've been pretty happy with their service. <br>
<br>One check for the original author. Are the DNS servers "recommended" at your install time in an Earthlink domain or Comcast one.</htmltext>
<tokenext>$ nslookup &gt; server 207.69.131.9 Default server : 207.69.131.9 Address : 207.69.131.9 # 53 &gt; comcast.sucks.com ; ; connection timed out ; no servers could be reached &gt; server www.microsoft.com Default server : www.microsoft.com Address : 207.46.193.254 # 53 Default server : www.microsoft.com Address : 207.46.192.254 # 53 &gt; comcast.sucks.com ; ; connection timed out ; no servers could be reached &gt; So when I point lookups at the comcast ad servers even , or Microsoft , the lookups fail .
Might be because we are on a business account here ( to get a block of static IPs ) but if our own captive ISP DNS servers are not reachable we 'd have problems as we have some internal non-standard stuff going on for our internal networking .
Our faked top level domain for our non-routable machines just would not show up .
Again , might be because we are business clients of Comcast , but they have done all sorts of things like capped our bandwidth , excessively applied traffic shaping , etc .
( corrected with a phone call mentioning we are business clients and \ _they \ _ committed to the usage rates we subscribed to .
) But other than a few glitches we 've been pretty happy with their service .
One check for the original author .
Are the DNS servers " recommended " at your install time in an Earthlink domain or Comcast one .</tokentext>
<sentencetext>
$ nslookup
&gt; server 207.69.131.9
Default server: 207.69.131.9
Address: 207.69.131.9#53
&gt; comcast.sucks.com ;; connection timed out; no servers could be reached
&gt; server www.microsoft.com
Default server: www.microsoft.com
Address: 207.46.193.254#53
Default server: www.microsoft.com
Address: 207.46.192.254#53
&gt; comcast.sucks.com ;; connection timed out; no servers could be reached
&gt; 

So when I point lookups at the comcast ad servers even, or Microsoft, the lookups fail.
Might be because we are on a business account here (to get a block of static IPs) but if our own captive ISP DNS servers are not reachable we'd have problems as we have some internal non-standard stuff going on for our internal networking.
Our faked top level domain for our non-routable machines just would not show up.
Again, might be because we are business clients of Comcast, but they have done all sorts of things like capped our bandwidth, excessively applied traffic shaping, etc.
(corrected with a phone call mentioning we are business clients and \_they\_ committed to the usage rates we subscribed to.
) But other than a few glitches we've been pretty happy with their service.
One check for the original author.
Are the DNS servers "recommended" at your install time in an Earthlink domain or Comcast one.</sentencetext>
</comment>
<comment>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270035</id>
	<title>Router hijacking DNS</title>
	<author>Mondo1287</author>
	<datestamp>1244578560000</datestamp>
	<modclass>None</modclass>
	<modscore>1</modscore>
	<htmltext>$20 says this guy's router is actually doing the hijacking and redirecting requests to the servers it receives via DHCP.</htmltext>
<tokenext>$ 20 says this guy 's router is actually doing the hijacking and redirecting requests to the servers it receives via DHCP .</tokentext>
<sentencetext>$20 says this guy's router is actually doing the hijacking and redirecting requests to the servers it receives via DHCP.</sentencetext>
</comment>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_73</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269573
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28274037
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269131
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270357
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270179
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270969
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269573
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269945
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270921
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270179
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270893
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_58</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269269
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270483
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_49</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269573
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28276543
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269809
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270511
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_65</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269131
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28280795
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_48</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269815
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270637
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_55</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269565
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270179
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270723
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269115
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270051
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_60</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270179
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270611
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275981
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269171
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269801
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269323
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270559
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269147
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270995
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_47</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269171
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270427
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_52</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269435
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28274547
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269131
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269637
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28280813
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_71</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269435
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28277199
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269131
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271229
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270499
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273097
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269251
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271813
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269289
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273189
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269171
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269253
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_69</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269131
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28292073
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269171
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269271
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270009
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_74</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269115
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269627
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_59</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270179
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28277627
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_50</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269131
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270613
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269581
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_64</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269263
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272927
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269633
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269999
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269131
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269637
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275077
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269633
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269923
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269573
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269755
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269633
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270455
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269573
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273581
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269435
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270683
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_56</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269251
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269481
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_72</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269949
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_63</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273923
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_46</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269263
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275339
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269295
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270221
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_62</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269093
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269771
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_53</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269097
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271371
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269563
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270615
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269147
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270943
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269171
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269275
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269131
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270651
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269365
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270699
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_54</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269215
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269885
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269181
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_68</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269147
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269539
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269115
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271557
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_61</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269365
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270469
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269365
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270425
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269251
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269621
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_75</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272267
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269435
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269893
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_51</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269633
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269853
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269633
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270441
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28282141
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269435
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273845
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269351
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269475
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_67</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271463
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275793
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_70</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269129
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269431
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269563
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272601
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_66</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269243
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_57</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269301
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270739
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269531
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270179
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272847
</commentlist>
</thread>
<thread>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#thread_09_06_09_1731238_27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269171
http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271549
</commentlist>
</thread>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.44</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269295
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270221
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.28</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270349
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.20</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271437
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.17</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271219
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.1</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269365
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270425
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270699
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270469
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.4</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269531
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270921
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270179
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270723
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270969
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270611
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272847
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270893
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28277627
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271463
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275793
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.35</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269077
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.18</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269263
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275339
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272927
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.11</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272953
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.40</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269809
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270511
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.36</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270021
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.30</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269289
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273189
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.9</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269441
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.43</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269633
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269923
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269853
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270441
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269999
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270455
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.27</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270387
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.12</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269017
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269215
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269885
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269097
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271371
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269475
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269251
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269481
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269621
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271813
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269131
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269637
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275077
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28280813
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270357
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270613
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28292073
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271229
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270651
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28280795
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.25</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269563
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270615
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272601
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.6</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269829
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.22</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269323
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270559
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.19</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270259
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.3</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269359
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.0</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269725
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.38</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272483
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.37</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270035
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.31</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273929
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.14</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273869
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.13</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270491
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.32</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269815
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270637
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.45</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269091
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269581
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273923
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28275981
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269171
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269253
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271549
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269801
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269275
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270427
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269271
---http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270009
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28282141
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28272267
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269181
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269351
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270499
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273097
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269565
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269949
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269243
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269301
--http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270739
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.29</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269837
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.21</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269085
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.8</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269269
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270483
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.42</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269147
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269539
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270943
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270995
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.26</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270791
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.39</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269385
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.24</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269453
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.15</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269109
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.5</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271941
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.2</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269093
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269771
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.33</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269399
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.16</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269115
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271557
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269627
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270051
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.41</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269435
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28277199
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270683
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28274547
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273845
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269893
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.34</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28271291
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.7</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269129
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269431
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.10</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28270323
</commentlist>
</conversation>
<conversation>
	<id>http://www.semanticweb.org/ontologies/ConversationInstances.owl#conversation09_06_09_1731238.23</id>
	<commentlist>http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269573
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28273581
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269755
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28269945
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28274037
-http://www.semanticweb.org/ontologies/ConversationInstances.owl#comment09_06_09_1731238.28276543
</commentlist>
</conversation>
