Replies: 1 comment
-
|
Thank you for this sugegstion @bandaid. The 31 different readme in this project are all generated from the readme_template.md file, and I would entertain a pull request with the edits you suggest. Closing. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
https://github.com/StevenBlack/hosts?tab=readme-ov-file#we-recommend-using-0000-instead-of-127001
The IPv4 address 127.0.0.1 belongs to the loopback block 127.0.0.0/8, which is reserved for internal host loopback traffic and is commonly used by services that bind only to the local machine. When a large hosts or lmhosts file maps thousands of domains to 127.0.0.1, every blocked connection is still sent through the loopback stack. On Windows this can add significant system and boot or logon latency and can interfere with software that legitimately listens on localhost.
By contrast, 0.0.0.0 is the IPv4 “unspecified” address, defined as a non routable special purpose address that must not be used as a normal destination. Mapping unwanted domains to 0.0.0.0 in the hosts file causes lookups to succeed at the HOSTS layer but makes connection attempts fail immediately, effectively blackholing those domains without touching localhost or any service bound to it.
A bare 0 is not a portable IPv4 address literal. Some Unix like networking stacks that implement historical inet_aton style parsing interpret 0 as 0.0.0.0, while other libraries and operating systems reject it as invalid. Because that behavior is not consistent across platforms, 0.0.0.0 is preferred over 0 as the reliable representation for this use.
Beta Was this translation helpful? Give feedback.
All reactions