Firefox directing to wwh

Hmm, never used to . . .

[rocknbil]

Somewhere amongst all the various updates to FireFox a new "feature" was installed. When I enter an invalid domain in the address bar it brings me to some search domain beginning in "wwh." I find this annoying. I'd rather have it go "nowhere".

I've dug through all the options and for the life of me cannot locate how to turn this off. Some of you probably know right where to look.

2.0.0.11 Windows XP Pro.

[coopster]

I just attempted the very same with a domain I own but have not set up pages yet. The registrar has "kindly" assigned their own Domain servers in listed order and it seems I am getting their default page for registered domains using their name servers and no hosting set up. Said page, oddly enough in this registrar's case, is a 404! hehehe.

However, if I key in an obviously unregistered domain name, such as www.example-example-example.com, in the address bar, I get the old default error page:

Server not found

---

Firefox can't find the server at www.example-example-example.com.

• Check the address for typing errors such as ww.example.com instead of www.example.com
  
• If you are unable to load any pages, check your computer's network connection.
  
• If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.

Try Again

I bet in your case the domain you keyed is registered but has no hosting setup. Run a whois on the domain and you'll find out soon enough.

[tedster]

I think coopster has the most likely explanation.

There is another possibility - a Firefox feature that you can control with about:config [kb.mozillazine.org]. It's the keyword.URL entry, which is activated or deactivated by the keyword.enabled entry. In default state, the keyword.URL uses Google's "I'm Feeling Lucky" results, but it can be set to use any URL or completely deactivated.

Note: the link above goes to a page about all the about:config user controls, not just the keyword.URL features.

[encyclo]

I believe this is not the browser at all - it is your ISP's DNS. When you are typing the non-existent domain, you are being redirected a site controlled by your ISP.

The solution would to be to use a different DNS provider (if you can) which has a more neutral approach and isn't trying to intercept your domain typos for their own gain.

[rocknbil]

encyclo is EXACTLY RIGHT! I never thought to test it in IE, but just like he's saying, they are hijacking my DNS for *any* browser. I just *presumed* it was some setting I was missing.

I am so fed up with these people, just last night we got slapped with an FAP when no one was using the comps here. It is a certain satellite provider. I will open a thread with some questions in the most appropriate forum, something has to be done. Enough is enough.

PS, encyclo your box is full, so . . .thank you. :-)

EDIT: OMG! Even after using the "opt out" service on this search engine . . . in FIREFOX . . . an invalid domain brings up . . . GUESS WHAT?

The Internet Explorer Page Not Found page! It even says "Microsoft Internet Explorer" at the bottom of the page . . . IN FIREFOX!

I wonder what MS will think of this.

[coopster]

So by "invalid" domain, you meant non-existent domain?

If I key in a non-existent domain, I get the default error page from Firefox (and no headers returned). I haven't monitored the traffic to see what is being sent/received from the pc yet though.

If I key a registered domain in which I have not yet modified the name servers, I get the registrar's default fallback page.

Boy, if your case is a non-existent domain and your ISP is monitoring and moving your destination I would be ticked too. I see [webmasterworld.com] you filed with the BBB, I'm interested to see how this turns out for you.

[tedster]

Verizon's FiOS service started doing this last spring (ConsumerAffairs.com article [consumeraffairs.com]) and it seems like the practice is spreading further. Reminds me of the Verisign Sitefinder fiasco in 2004 (ZDnet story [zdnet.com.au])

Good to know it's not a Firefox issue.

[coopster]

True, but even worse to know that ISP's are playing around with your requests!