Remove :: and 0.0.0.0 from private #2780
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Originally posted at MetaCubeX/meta-rules-dat#98, copying to here,
Hi, according to section 3 of IETF RFC 5735 and RFC 1122 3.2.1.3 (a), addresses in
0.0.0.0/8,And according to RFC 4291 2.5.2, the
::,No client in a normal case would even try to request such addresses.
In the real world, the IPv4 address
0.0.0.0and IPv6 address::are used by ISPs and enterprise networks to block access to a specific domain on the DNS level. And in most practices, theprivateruleset is set to direct connection, which would cause these blocked sites to be proxied in the end, went direct and failed.Thus, they shall be removed for a better user experience.