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.

Learn More

Not fixed: Re: MAJOR BUG: Firefox ignores the hosts file

  • 2 balasan
  • 8 ada masalah ini
  • 1 paparan
  • Balasan terakhir oleh Felicia

more options

A previous issue that was created here, https://support.mozilla.org/en-US/questions/1011327, is not resolved. Firefox's behavior is simply wrong.

The problem has to do with Firefox searching strings in the the address bar when no keyword is specified.

If I type the name of a host in my machine's host file, Firefox should behave like any other app (for example ping) and consult the hosts file.

But instead it assumes that the string is something the user wants to search for. This without the user having entered a keyword for a search.

For example if a user has the keyword g set to search google.com, then if they enter "g somestring" in the address bar, it *should* search google for somestring.

But if the user enters "somestring" alone in the address bar, Firefox should not force a search for it, completely bypassing the hosts file.

A previous issue that was created here, https://support.mozilla.org/en-US/questions/1011327, is not resolved. Firefox's behavior is simply wrong. The problem has to do with Firefox searching strings in the the address bar when no keyword is specified. If I type the name of a host in my machine's host file, Firefox should behave like any other app (for example ping) and consult the hosts file. But instead it assumes that the string is something the user wants to search for. This without the user having entered a keyword for a search. For example if a user has the keyword g set to search google.com, then if they enter "g somestring" in the address bar, it *should* search google for somestring. But if the user enters "somestring" alone in the address bar, Firefox should not force a search for it, completely bypassing the hosts file.

Penyelesaian terpilih

Firefox has changed a lot since that old thread, but the current default behavior is to search first and check DNS in the background. When Firefox detects a hostname, it should display an infobar asking if you wanted to access that hostname, and then if you click through, add a preference to do that from now on for that hostname. I have attached a screen shot illustrating this.

To force Firefox to do a DNS lookup first, you can use this setting:

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful.

(2) In the search box above the list, type or paste fix and pause while the list is filtered

(3) Double-click the browser.fixup.dns_first_for_single_words preference to switch it from false to true

Does that work for you?

Baca jawapan ini dalam konteks 👍 2

All Replies (2)

more options

Penyelesaian Terpilih

Firefox has changed a lot since that old thread, but the current default behavior is to search first and check DNS in the background. When Firefox detects a hostname, it should display an infobar asking if you wanted to access that hostname, and then if you click through, add a preference to do that from now on for that hostname. I have attached a screen shot illustrating this.

To force Firefox to do a DNS lookup first, you can use this setting:

(1) In a new tab, type or paste about:config in the address bar and press Enter/Return. Click the button promising to be careful.

(2) In the search box above the list, type or paste fix and pause while the list is filtered

(3) Double-click the browser.fixup.dns_first_for_single_words preference to switch it from false to true

Does that work for you?

more options

Thanks that is the solution! Works perfectly now!