Repository files navigation

This project manages a list of domains, to be used as geosites for routing purpose in Project V.

This project is not opinionated. In other words, it does NOT endorse, claim or imply that a domain should be blocked or proxied. It can be used to generate routing rules on demand.

• dlc.dat：https://github.com/v2fly/domain-list-community/releases/latest/download/dlc.dat
• dlc.dat.sha256sum：https://github.com/v2fly/domain-list-community/releases/latest/download/dlc.dat.sha256sum

Each file in thedata directory can be used as a rule in this format:geosite:filename.

"routing": {"domainStrategy":"IPIfNonMatch","rules": [    {"type":"field","outboundTag":"Reject","domain": ["geosite:category-ads-all","geosite:category-porn"      ]    },    {"type":"field","outboundTag":"Direct","domain": ["domain:icloud.com","domain:icloud-content.com","domain:cdn-apple.com","geosite:cn","geosite:private"      ]    },    {"type":"field","outboundTag":"Proxy-1","domain": ["geosite:category-anticensorship","geosite:category-media","geosite:category-vpnservices"      ]    },    {"type":"field","outboundTag":"Proxy-2","domain": ["geosite:category-dev"      ]    },    {"type":"field","outboundTag":"Proxy-3","domain": ["geosite:geolocation-!cn"      ]    }  ]}

• Installgolang andgit
• Clone project code:git clone https://github.com/v2fly/domain-list-community.git
• Navigate to project root directory:cd domain-list-community
• Install project dependencies:go mod download
• Generatedlc.dat (withoutdatapath option means to use domain lists indata directory of current working directory):
  • go run ./
  • go run ./ --datapath=/path/to/your/custom/data/directory

Rungo run ./ --help for more usage information.

All data are underdata directory. Each file in the directory represents a sub-list of domains, named by the file name. File content is in the following format.

# commentsinclude:another-filedomain:google.com @attr1 @attr2keyword:googleregexp:www\.google\.com$full:www.google.com

Syntax:

The following types of rules areNOT fully compatible with the ones that defined by user in V2Ray config file. DoNot copy and paste directly.

• Comment begins with#. It may begin anywhere in the file. The content in the line after# is treated as comment and ignored in production.
• Inclusion begins withinclude:, followed by the file name of an existing file in the same directory.
• Subdomain begins withdomain:, followed by a valid domain name. The prefixdomain: may be omitted.
• Keyword begins withkeyword:, followed by a string.
• Regular expression begins withregexp:, followed by a valid regular expression (per Golang's standard).
• Full domain begins withfull:, followed by a complete and valid domain name.
• Domains (includingdomain,keyword,regexp andfull) may have one or more attributes. Each attribute begins with@ and followed by the name of the attribute.

The entiredata directory will be built into an externalgeosite file for Project V. Each file in the directory represents a section in the generated file.

To generate a section:

1. Remove all the comments in the file.
2. Replaceinclude: lines with the actual content of the file.
3. Omit all empty lines.
4. Generate eachdomain: line into asub-domain routing rule.
5. Generate eachkeyword: line into aplain domain routing rule.
6. Generate eachregexp: line into aregex domain routing rule.
7. Generate eachfull: line into afull domain routing rule.

Theoretically any string can be used as the name, as long as it is a valid file name. In practice, we prefer names for determinic group of domains, such as the owner (usually a company name) of the domains, e.g., "google", "netflix". Names with unclear scope are generally unrecommended, such as "evil", or "local".

Attribute is useful for sub-group of domains, especially for filtering purpose. For example, the list ofgoogle domains may contains its main domains, as well as domains that serve ads. The ads domains may be marked by attribute@ads, and can be used asgeosite:google@ads in V2Ray routing.

• Fork this repo, make modifications to your own repo, file a PR.
• Please begin with small size PRs, say modification in a single file.
• A PR must be reviewed and approved by another member.
• A script will verify your pull request to test whether your PR is correct or not every time you update the PR. Only the PR which passes the test will be merged. Please go to the Action label to get detailed information if you didn't pass it. We also provide the file which has been generated to make you test.
• After a few successful PRs, you may apply for manager access to this repository.