<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: RCN Hijacking Mistyped URLs</title>
	<atom:link href="http://blog.edhayes.us/2009/08/05/rcn-hijacking-mistyped-urls/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.edhayes.us/2009/08/05/rcn-hijacking-mistyped-urls/</link>
	<description>Information Technology, Business Consulting, and Solutions to Life</description>
	<lastBuildDate>Wed, 25 Aug 2010 01:52:41 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Josh Brinkman</title>
		<link>http://blog.edhayes.us/2009/08/05/rcn-hijacking-mistyped-urls/#comment-566</link>
		<dc:creator>Josh Brinkman</dc:creator>
		<pubDate>Wed, 10 Feb 2010 15:30:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.edhayes.us/?p=279#comment-566</guid>
		<description>I guess I&#039;m late to this party, but I&#039;ve been living with this situation for a while now.  My problem differs from you all because I need to use a Virtual Private Networking client to connect to my office.  RCN (randomly it seems) intercepts all DNS lookups, no matter what protocol.  If I ping a hostname in my company&#039;s internal network, I frequently get back an RCN IP address, and sometimes I get back the real machine address.  This is even more annoying because I need to first log into my company&#039;s firewall (via http) before accessing any machines.  RCN hates to let me get to the firewall so I can type in my credentials... they always redirect to their search results page.</description>
		<content:encoded><![CDATA[<p>I guess I&#8217;m late to this party, but I&#8217;ve been living with this situation for a while now.  My problem differs from you all because I need to use a Virtual Private Networking client to connect to my office.  RCN (randomly it seems) intercepts all DNS lookups, no matter what protocol.  If I ping a hostname in my company&#8217;s internal network, I frequently get back an RCN IP address, and sometimes I get back the real machine address.  This is even more annoying because I need to first log into my company&#8217;s firewall (via http) before accessing any machines.  RCN hates to let me get to the firewall so I can type in my credentials&#8230; they always redirect to their search results page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed Hayes</title>
		<link>http://blog.edhayes.us/2009/08/05/rcn-hijacking-mistyped-urls/#comment-512</link>
		<dc:creator>Ed Hayes</dc:creator>
		<pubDate>Mon, 23 Nov 2009 00:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.edhayes.us/?p=279#comment-512</guid>
		<description>Very simplified, when you request a non existent URL, let&#039;s say &#039;nonexistent.com&#039;, your computer asks your router where it is.  Your router doesn&#039;t know, so it asks your ISP.  In this case, your Internet Service Provider, RCN, says &quot;we don&#039;t know where that is, but we&#039;ll send you to our page, with &#039;nonexistent.com&#039; as the search results.&quot;  Then they make money from the ads on that page.</description>
		<content:encoded><![CDATA[<p>Very simplified, when you request a non existent URL, let&#8217;s say &#8216;nonexistent.com&#8217;, your computer asks your router where it is.  Your router doesn&#8217;t know, so it asks your ISP.  In this case, your Internet Service Provider, RCN, says &#8220;we don&#8217;t know where that is, but we&#8217;ll send you to our page, with &#8216;nonexistent.com&#8217; as the search results.&#8221;  Then they make money from the ads on that page.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cynthia Ross</title>
		<link>http://blog.edhayes.us/2009/08/05/rcn-hijacking-mistyped-urls/#comment-511</link>
		<dc:creator>Cynthia Ross</dc:creator>
		<pubDate>Sun, 22 Nov 2009 23:48:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.edhayes.us/?p=279#comment-511</guid>
		<description>Wow, can they actually do that? I always thought if you typed an incorrect URL you should get the error message.</description>
		<content:encoded><![CDATA[<p>Wow, can they actually do that? I always thought if you typed an incorrect URL you should get the error message.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chilled Out Bearded Man&#187; Blog Archive &#187; RCN Hijacks Mistyped URLs</title>
		<link>http://blog.edhayes.us/2009/08/05/rcn-hijacking-mistyped-urls/#comment-505</link>
		<dc:creator>Chilled Out Bearded Man&#187; Blog Archive &#187; RCN Hijacks Mistyped URLs</dc:creator>
		<pubDate>Tue, 10 Nov 2009 05:23:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.edhayes.us/?p=279#comment-505</guid>
		<description>[...] finally got on my nerves today and I decided to search for a solution. At first I found this article titled RCN Hijacking Mistyped URLs by Ed Hayes which recommended calling RCN as he had done. I didn&#8217;t want to call them, so I spent a few [...]</description>
		<content:encoded><![CDATA[<p>[...] finally got on my nerves today and I decided to search for a solution. At first I found this article titled RCN Hijacking Mistyped URLs by Ed Hayes which recommended calling RCN as he had done. I didn&#8217;t want to call them, so I spent a few [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed Hayes</title>
		<link>http://blog.edhayes.us/2009/08/05/rcn-hijacking-mistyped-urls/#comment-483</link>
		<dc:creator>Ed Hayes</dc:creator>
		<pubDate>Thu, 05 Nov 2009 16:39:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.edhayes.us/?p=279#comment-483</guid>
		<description>Yes, OpenDNS will solve the problem.  To test it, just make the change to your router or PC&#039;s DNS server settings, and go to a fake server.</description>
		<content:encoded><![CDATA[<p>Yes, OpenDNS will solve the problem.  To test it, just make the change to your router or PC&#8217;s DNS server settings, and go to a fake server.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RCharles</title>
		<link>http://blog.edhayes.us/2009/08/05/rcn-hijacking-mistyped-urls/#comment-482</link>
		<dc:creator>RCharles</dc:creator>
		<pubDate>Thu, 05 Nov 2009 10:32:31 +0000</pubDate>
		<guid isPermaLink="false">http://blog.edhayes.us/?p=279#comment-482</guid>
		<description>I went through this with RCN a while back, with no confidence they actually had disabled the URL interception.

I then programmed my wi-fi router to use specific IP address for DNS server, e.g., 4.2.2.1  My understanding that this should bypass RCNs DNS system and, therefore, the URL intercept function as well.

Can anyone confirm that using public DNS servers solves this problem?

Is there a way to test this arrangement and prove that it works?

Thanks

Ray</description>
		<content:encoded><![CDATA[<p>I went through this with RCN a while back, with no confidence they actually had disabled the URL interception.</p>
<p>I then programmed my wi-fi router to use specific IP address for DNS server, e.g., 4.2.2.1  My understanding that this should bypass RCNs DNS system and, therefore, the URL intercept function as well.</p>
<p>Can anyone confirm that using public DNS servers solves this problem?</p>
<p>Is there a way to test this arrangement and prove that it works?</p>
<p>Thanks</p>
<p>Ray</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Boone, CPA</title>
		<link>http://blog.edhayes.us/2009/08/05/rcn-hijacking-mistyped-urls/#comment-481</link>
		<dc:creator>Matt Boone, CPA</dc:creator>
		<pubDate>Wed, 04 Nov 2009 20:28:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.edhayes.us/?p=279#comment-481</guid>
		<description>Oh, and I forgot to mention that the issue is now resolved.  Time to donate more money to the Net Neutrality people.</description>
		<content:encoded><![CDATA[<p>Oh, and I forgot to mention that the issue is now resolved.  Time to donate more money to the Net Neutrality people.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Matt Boone, CPA</title>
		<link>http://blog.edhayes.us/2009/08/05/rcn-hijacking-mistyped-urls/#comment-480</link>
		<dc:creator>Matt Boone, CPA</dc:creator>
		<pubDate>Wed, 04 Nov 2009 20:25:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.edhayes.us/?p=279#comment-480</guid>
		<description>I went to the RCN website and completed the &quot;Contact Us&quot; form for tech support.  I typed, &quot;Please disable your DNS hijacking service called &quot;FoxFire.&quot;  About an hour later I received an email from their tech support that said the following:

Dear Mr. Boone,

My apologies for the inconvenience. About the redirects, the reason we had this on our system is that if ever you made a mistake or entered search terms into your address bar while using a web browser, the new service tries helping you find what you are looking for, similar to a toolbar function, without the need to install a toolbar.

But since this is quite inconvenient on your end, I will be disabling this setting on your end so that you connection will go back to the way it was. And just to complete this process, can you please power cycle all of your equipments.

SEQUENTIAL POWER CYCLE (with wireless router)

1. Turn OFF the computer. (Complete shutdown)

2. Turn OFF the wireless router. (Unplug power cord from the router)

3. Turn OFF the cable modem. (Unplug power cord from the cable modem).

4. Leave it OFF for about a minute or two.

5. Turn ON cable modem first. (Give it a minute to reboot)

6. Turn ON wireless router. (Give it another minute to reboot)

7. Turn ON computer and then try to get online to the internet.

Or you could also try these steps.

POWER CYCLE (without the wireless router)

1. Turn OFF the computer. (Complete shutdown)

2. Turn OFF the cable modem. (Unplug power cord from the cable modem).

3. Leave it OFF for about a minute or two.

4. Turn ON cable modem first. (Give it a minute to reboot)

5. Turn ON computer and then try to get online to the internet.

I hope these steps could help you with your issue. Should you have any further questions or concerns, please feel free to contact us on your most convenient time.

Thank you,

Bessy

RCN Email Support

1-800-746-4726 (toll free)

1-610-443-5550 (toll fees apply)

RCN - Connect to Something More.</description>
		<content:encoded><![CDATA[<p>I went to the RCN website and completed the &#8220;Contact Us&#8221; form for tech support.  I typed, &#8220;Please disable your DNS hijacking service called &#8220;FoxFire.&#8221;  About an hour later I received an email from their tech support that said the following:</p>
<p>Dear Mr. Boone,</p>
<p>My apologies for the inconvenience. About the redirects, the reason we had this on our system is that if ever you made a mistake or entered search terms into your address bar while using a web browser, the new service tries helping you find what you are looking for, similar to a toolbar function, without the need to install a toolbar.</p>
<p>But since this is quite inconvenient on your end, I will be disabling this setting on your end so that you connection will go back to the way it was. And just to complete this process, can you please power cycle all of your equipments.</p>
<p>SEQUENTIAL POWER CYCLE (with wireless router)</p>
<p>1. Turn OFF the computer. (Complete shutdown)</p>
<p>2. Turn OFF the wireless router. (Unplug power cord from the router)</p>
<p>3. Turn OFF the cable modem. (Unplug power cord from the cable modem).</p>
<p>4. Leave it OFF for about a minute or two.</p>
<p>5. Turn ON cable modem first. (Give it a minute to reboot)</p>
<p>6. Turn ON wireless router. (Give it another minute to reboot)</p>
<p>7. Turn ON computer and then try to get online to the internet.</p>
<p>Or you could also try these steps.</p>
<p>POWER CYCLE (without the wireless router)</p>
<p>1. Turn OFF the computer. (Complete shutdown)</p>
<p>2. Turn OFF the cable modem. (Unplug power cord from the cable modem).</p>
<p>3. Leave it OFF for about a minute or two.</p>
<p>4. Turn ON cable modem first. (Give it a minute to reboot)</p>
<p>5. Turn ON computer and then try to get online to the internet.</p>
<p>I hope these steps could help you with your issue. Should you have any further questions or concerns, please feel free to contact us on your most convenient time.</p>
<p>Thank you,</p>
<p>Bessy</p>
<p>RCN Email Support</p>
<p>1-800-746-4726 (toll free)</p>
<p>1-610-443-5550 (toll fees apply)</p>
<p>RCN &#8211; Connect to Something More.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RCN DNS Redirect in Boston and How to Opt Out - Unlikely Words - A blog of Boston, Providence, and the world</title>
		<link>http://blog.edhayes.us/2009/08/05/rcn-hijacking-mistyped-urls/#comment-475</link>
		<dc:creator>RCN DNS Redirect in Boston and How to Opt Out - Unlikely Words - A blog of Boston, Providence, and the world</dc:creator>
		<pubDate>Wed, 28 Oct 2009 18:16:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.edhayes.us/?p=279#comment-475</guid>
		<description>[...] my account for an opt out before sending an email to RCN Customer Service. I would have called, but this post made me think I&#8217;d be better off emailing them and waiting for a reply instead of [...]</description>
		<content:encoded><![CDATA[<p>[...] my account for an opt out before sending an email to RCN Customer Service. I would have called, but this post made me think I&#8217;d be better off emailing them and waiting for a reply instead of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed Hayes</title>
		<link>http://blog.edhayes.us/2009/08/05/rcn-hijacking-mistyped-urls/#comment-474</link>
		<dc:creator>Ed Hayes</dc:creator>
		<pubDate>Tue, 20 Oct 2009 02:43:56 +0000</pubDate>
		<guid isPermaLink="false">http://blog.edhayes.us/?p=279#comment-474</guid>
		<description>Gant,  RCN can turn it off on your entire account if you call them.  The solution Paxfire likely gave you was to use the cookie solution or something of that nature.  That does not turn it off, it just hides it.</description>
		<content:encoded><![CDATA[<p>Gant,  RCN can turn it off on your entire account if you call them.  The solution Paxfire likely gave you was to use the cookie solution or something of that nature.  That does not turn it off, it just hides it.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
