Selected ISP Support > DSL Extreme > redirects to look-up-results.com

reply to socio

Re: redirects to look-up-results.com

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.

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.

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.

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

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.

> Try using 4.2.2.2, 4.2.2.3.

Thanks for the tip, Djdeadly. Indeed they do provide great latency from where I am.

But I still consider the new "feature" a bug. Besides, it won't help with the stated problem - non-existing domains do not return a 404 code; there is no http server to respond. My browser (Firefox) responds with an alert that the site "could not be found. Check the name and try again." If that is too confusing take it up with the browser folks, but don't muck with DNS.

P.S. Two other points: A major change like this should have been communicated to your customers. And don't expect all your customers to know that this is the forum where they can learn which DNS server to use.