This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

ఇంకా తెలుసుకోండి

Location bar search goes to my internet service provider instead of search engine selected in search bar; why?

  • 6 ప్రత్యుత్తరాలు
  • 10 ఈ సమస్యలు కలిగి ఉన్నాయి
  • 1 వీక్షణ
  • చివరి సమాధానమిచ్చినది cnshht

more options

Using Firefox 26.0 for openSUSE 12.3

I have disabled keyword search from the location/address bar, because instead of search results from the source selected in the search bar (google), my string entry got sent to my internet service provider, some kind of dead-end, unproductive "web search" page with no results.

I had typed in "ezsniper" to the location bar. After disabling the keyword search in about:config, my string entry took me to ezsniper.com, which is better than the dead-end Charter.com page

Using Firefox 26.0 for openSUSE 12.3 I have disabled keyword search from the location/address bar, because instead of search results from the source selected in the search bar (google), my string entry got sent to my internet service provider, some kind of dead-end, unproductive "web search" page with no results. I had typed in "ezsniper" to the location bar. After disabling the keyword search in about:config, my string entry took me to ezsniper.com, which is better than the dead-end Charter.com page

ఎంపిక చేసిన పరిష్కారం

I've set my DNS addresses to 8.8.8.8 and 8.8.4.4 (Google Public DNS)

The problem has not happened again, but stopped before I made the DNS change. Charter Communications seemed to allow a way to turn off the "service" that had ignored my browser/preferences, so that might have done it.... I appreciate the responses, doubt Charter will get another chance to hijack DNS again.

ఈ సందర్భంలో ఈ సమాధానం చదవండి 👍 0

ప్రత్యుత్తరాలన్నీ (6)

more options

After resetting the config setting mentioned above to the default (true) value again, and restarting firefox, the same string and any others entered in the location bar correctly were sent to the search provider selected in my search bar.

The only other thing that might have affected this is that I had recently made a temporary change to the selected search provider. But this had been reset to google before the above described search was misdirected to the internet service provider.

more options

those useless pages are normally served through your ISP on invalid DNS requests. another way to mitigate that would be to configure your system to use an alternative DNS server like the one google provides: https://developers.google.com/speed/public-dns

more options
more options

ఎంపిక చేసిన పరిష్కారం

I've set my DNS addresses to 8.8.8.8 and 8.8.4.4 (Google Public DNS)

The problem has not happened again, but stopped before I made the DNS change. Charter Communications seemed to allow a way to turn off the "service" that had ignored my browser/preferences, so that might have done it.... I appreciate the responses, doubt Charter will get another chance to hijack DNS again.

more options

There is this page however not sure if it is cookie based or if once you opt out it will not matter what browser is used or if cookies are removed. http://search.charter.net/prefs.php

more options

Yep, James, this is the page where I attempted to disable the Charter Communications "Web Helper."

      But on revisiting the page, I see that it is nevertheless "enabled."  (So I have "disabled" it again, and an immediate recheck shows it is "disabled."  Guessing it defaults back to "enabled" if/ when cookies are cleared, which is sometimes needed to avoid other unsolicited "help."

Hopefully using Google Public DNS will prevent Charter from "helping" me any more with my "website preferences"! Thanks again to all who have addressed this issue.