socio
join:2005-09-30
San Gabriel, CA
|  redirects to look-up-results.com
I noticed today that an intercept is happening in my web browser that triggers a search result from look-up-results.com. This is happening in two different places under two different DSLX accounts, so I'm led to believe this is something being done at the ISP level.
I haven't seen this announced anywhere, and frankly, I would rather that the intercept/search not happen. On my Mac, if I type "apple" in the URL and hit enter, instead of allowing the browser to add the "www" and "com" to tbe front and back, respectively, I get a search result from look-up-result.com, which is annoying.
I don't use a PC as much, so I haven't seen the impact there, but regardless, I would like to see this "feature" to be off by default, instead of having to hunt down the obscure "About" link at the bottom of a search result to opt-out (via a cookie). |
|
The Way Out
join:2003-01-20 | Sounds like it's a "feature" of your browser. DSLX has no control over how your browser handles the word "apple." |
|
socio
join:2005-09-30
San Gabriel, CA
1 edit | It's not my browser doing it. I tested this on three different systems in two locations on two different DSLX accounts, and a call to tech support confirmed that this is being done at the ISP level.
The About link describes the service as: " This service automatically eliminates dead-end "error" pages you encounter as you surf the web. Absolutely no software was installed on your computer for this service to work. This search tool is designed to make your web surfing experience more productive" along with an option to opt-out via accepting a cookie.
If I try going to a non-existant/invalid URL, normally I'd get a 404, but with this intercept going on, I get a search result from look-up-result.com that tells me the page doesn't exist along with side banner ads. In the case of my entering "apple" on a Mac, where the browser would normally go to www.apple.com, I instead get search results on the term "apple." |
|
The Way Out
join:2003-01-20
| I seriously doubt that DSLX is doing Layer 7 filtering on your traffic. Post more details about your problem. State what browser you're using on what OS, as well as EXACTLY what you're typing in to triger this issue. I'm still not convinced that this is anywhere related to a DSLX problem. |
|
socio
join:2005-09-30
San Gabriel, CA
| said by The Way Out  :I seriously doubt that DSLX is doing Layer 7 filtering on your traffic. Post more details about your problem. State what browser you're using on what OS, as well as EXACTLY what you're typing in to triger this issue. I'm still not convinced that this is anywhere related to a DSLX problem. If I enter some random URL, such as »www.hjsskjf.com, instead of a 404, I am sent to:
»wwa.look-up-results.com/search?q···73396951
This is happening in Firefox (WinXP and OS X) as well as IE 6 (Win XP) and Safari (OS X). The WinXp box is at a business location and the OS X box is at a residence, both of which are in two different parts of L.A. and on different DSLX accounts. |
|
The Way Out
join:2003-01-20 | If it really is happening across browsers and OSs, you've probably got poisoned DNS servers on your system. Better make sure you're using known-good DNS servers. |
|
socio
join:2005-09-30
San Gabriel, CA
| said by The Way Out :If it really is happening across browsers and OSs, you've probably got poisoned DNS servers on your system. Better make sure you're using known-good DNS servers. Thanks for the suggestion, but the DNS servers are gotten via DHCP and tech support says they know about this "feature" and that it is something they began rolling out yesterday. |
|
Djdeadly
join:2000-11-03
San Jose, CA | reply to socio
Set your primary DNS to 4.2.2.2 and secondary to one of DSLextreme's IPs. |
|
getzagogo999
join:2006-04-04
Salt Lake City, UT | This search service is easy to make go away. Just go to the bottom of the page and click About and opt out. |
|
The Way Out
join:2003-01-20
| reply to socio
Holy crap, so they have.
$ dig www.hjsskjf.com @66.51.206.100
; > DiG 8.4 > www.hjsskjf.com @66.51.206.100
;; ANSWER SECTION:
www.hjsskjf.com. 1M IN A 64.158.56.40
It lokos like the 66.218.44.5 DNS server doesn't have this stuff on it yet. Use that, or the Level3 DNS servers as posted above.
George: What's going on over there? |
|
dslx_gm
Premium,VIP
join:2002-12-26
Winnetka, CA
| reply to socio
Due to an increased number of support calls from our non internet savvy clients getting 404 errors, we are currently testing a new system on one of our DNS servers in the pool. If the DNS server is unable to resolve the site that is entered the system will return a list of possible site suggestions. This is done via a pass through and not layer 7 filtering of your traffic. Our more internet savvy clients have the option to opt of using the system by selecting the about link at the bottom of the page.
We hope that the system will help reduce support calls and increase our level of support for true technical problems. This is a trial to determine if it actually reduces the number of 404 error support calls. We have made sure that there is an opt-out procedure for clients who do not wish to use the system.
--
George
General Manager
DSLExtreme
Will work for reviews.  |
|
piersden
join:2005-10-31
Los Angeles, CA
|  reply to socio
George, this is a TERRIBLE feature. Since I, like many others, clear all cookies daily or sometimes several times daily, this means going through opt-out process each time. Also, normally this would process would go via Google, but after opting out and then entering a random URL--such as Dell or CNET--MSN search pops up instead of Google. Do you, or anyone out there, have any suggestions? Could we just go back to the way things were?? This is very frustrating. |
|
getzagogo999
join:2006-04-04
Salt Lake City, UT | I found another way to get out of it. On my PC, just installed the Google toolbar. Normally IE would just go to MSN search results page for a keyword. |
|
piersden
join:2005-10-31
Los Angeles, CA
| reply to socio
I use Firefox, not IE. Before, address keyword automatically used Google, now it's using MSN. Don't really want/need another toolbar (i.e. Google), just want everything back the way it was before DSLExtreme decided to experiment with this new system. |
|
dslx_gm
Premium,VIP
join:2002-12-26
Winnetka, CA
| reply to piersden
Hi piersden -
I use Firefox and have my system set to clear my cookies fairly frequently as well. In order avoid logging into sites like BBR that I frequently visit, I setup cookie exceptions in Firefox. To do this go to Tools | Options and select the cookies tab. After selecting the exceptions button add in the site look-up-results.com. This will store the cookie permanently so you won't see any changes in your browsing experience while we are testing the system.
Thanks
--
George
General Manager
DSLExtreme
Will work for reviews. |
|
gobbledygook
join:2006-04-05
| This just doesn't work.
Some of us use our computers for things other than web browsing. And we set up our systems to take a specific action when a DNS lookup failure occurs. This doesn't work now, and cannot be fixed with cookies (cookies have no meaning outside of http services).
If you insist in offering this "feature", you should also provide other DNS servers that work the way DNS was intended to, with an equivalent low latency. |
|
Djdeadly
join:2000-11-03
San Jose, CA
1 edit | I'm guessing everybody is ignoring my post.
Try using 4.2.2.2, 4.2.2.3. It uses AnyCast tech so the nearest DNS server will respond to your requests.
»en.wikipedia.org/wiki/Anycast
Pinging 4.2.2.2 with 32 bytes of data:
Reply from 4.2.2.2: bytes=32 time=10ms TTL=250
Reply from 4.2.2.2: bytes=32 time=10ms TTL=250
Reply from 4.2.2.2: bytes=32 time=10ms TTL=250
Reply from 4.2.2.2: bytes=32 time=9ms TTL=250
Ping statistics for 4.2.2.2:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 10ms, Average = 9ms
NorCal DNS
Pinging 66.218.44.5 with 32 bytes of data:
Reply from 66.218.44.5: bytes=32 time=9ms TTL=61
Reply from 66.218.44.5: bytes=32 time=9ms TTL=61
Reply from 66.218.44.5: bytes=32 time=12ms TTL=61
Reply from 66.218.44.5: bytes=32 time=9ms TTL=61
Ping statistics for 66.218.44.5:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 9ms, Maximum = 12ms, Average = 9ms
Tracing route to vnsc-bak.sys.gtei.net [4.2.2.2]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 11 ms 10 ms netblock-66-245-255-1.dslextreme.com [66.245.255.1]
3 10 ms 10 ms 10 ms SJC1.CR1.Gig6-0-20.dslextreme.com [66.218.44.57]
4 11 ms 10 ms 10 ms ge-8-0-142.ipcolo2.SanJose1.Level3.net [63.215.203.65]
5 11 ms 10 ms 10 ms ge-11-0.core1.SanJose1.Level3.net [4.68.123.38]
6 11 ms 11 ms 10 ms vnsc-bak.sys.gtei.net [4.2.2.2]
Trace complete.
Tracing route to netblock-66-218-44-90.dslextreme.com [66.218.44.90]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms 192.168.1.1
2 13 ms 10 ms 9 ms netblock-66-245-255-1.dslextreme.com [66.245.255
.1]
3 10 ms 11 ms 10 ms SJC1.CR1.Gig6-0-20.dslextreme.com [66.218.44.57]
4 11 ms 10 ms 10 ms netblock-66-218-44-90.dslextreme.com [66.218.44.
90]
Trace complete.
2 more hops but just as fast. |
|
OZO
Premium
join:2003-01-17
| reply to dslx_gm
Please do not do that!!!
I really hope that you guys remember what was happened a while ago when the same "feature" was implemented for some TLD. Do not repeat the same mistake again!
You make your DNS unusable for your loyal users and make them think about that kind of "service"...
--
Keep it simple, it'll become complex by itself... |
|
wa2000
join:2001-02-21
Rosemead, CA | reply to dslx_gm
Please remove this "feature"........ |
|
brmehlman
join:2005-05-21
Richmond, CA
1 edit | reply to socio
It's not a feature, it's a bug. A deliberately induced bug, but a bug nevertheless.
quote:
Due to an increased number of support calls from our non internet savvy clients getting 404 errors ...
Bull. You want to post here and say you're not getting paid for those redirects?
added later: I'm speaking hearsay, it hasn't happened to me. My dns failures are normal, and I sure hope they stay that way. |
|
