New
#1
Hosts File Not Working Firefox
Hello again,
My hosts file will only block sites in Edge, not in Firefox.
Can't be right. Any ideas ?
Windows 10 1909
Regards
Nordland
Hello again,
My hosts file will only block sites in Edge, not in Firefox.
Can't be right. Any ideas ?
Windows 10 1909
Regards
Nordland
Who is your ISP and do they support using IPv6? Your HOSTS file may only be blocking IPv4 addresses.
) It probably is ...
It's so short that making a zip of it wouldn't achieve much. Copy/pasted here:
# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
#
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
#
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
#
# For example:
#
# 102.54.94.97 rhino.acme.com # source server
# 38.25.63.10 x.acme.com # x client host
# localhost name resolution is handled within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
127.0.0.1 mikrotik.com
Regards
Nordland
Deleting the last line gives you an empty hosts file, which may be fine. Doesn't explain your statement that it blocks in Edge, not Firefox. Is this the legacy Edge or Edge Chromium (new one)?
FYI: mikrotik.com is a Router Manufacturer out of Latvia.
"MikroTik is a Latvian company which was founded in 1996 to develop routers and wireless ISP systems."
MikroTik Routers and Wireless
Apparently Firefox likes www before the domain name -
Example -
127.0.0.1 www.tenforums.com
As far as I know you can add both entries with and without www
Quote from another source:
So I always use 0.0.0.0The HOSTS file now contains a change in the prefix in the HOSTS entries to "0.0.0.0" instead of the usual "127.0.0.1".
This was done to resolve a slowdown issue that occurs with the change Microsoft made in the "TCP loopback interface"
Using 0.0.0.0 is empirically faster, possibly because there's no wait for a timeout resolution.
Tested with Firefox 78.0.1
Did not work without the www prefix...for me.
The www prefix worked in both Firefox and new Edge.