mirror of
https://github.com/v2fly/domain-list-community.git
synced 2026-03-23 20:06:12 +07:00
Compare commits
9 Commits
2026031810
...
2026032204
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
c9348f1db4 | ||
|
|
d62599c8db | ||
|
|
fab6275217 | ||
|
|
4c7afec5a9 | ||
|
|
330c30eb23 | ||
|
|
f34f22819e | ||
|
|
baa1409cfb | ||
|
|
a22d247c5a | ||
|
|
d311bbe50b |
@@ -86,6 +86,8 @@ Each file in the `data` directory can be used as a rule in this format: `geosite
|
||||
|
||||
Run `go run ./ --help` for more usage information.
|
||||
|
||||
For anyone who wants to generate custom `.dat` files, you may read [#3370](https://github.com/v2fly/domain-list-community/discussions/3370).
|
||||
|
||||
## Structure of data
|
||||
|
||||
All data are under `data` directory. Each file in the directory represents a sub-list of domains, named by the file name. File content is in the following format.
|
||||
@@ -105,7 +107,7 @@ regexp:^odd[1-7]\.example\.org(\.[a-z]{2})?$
|
||||
> Adding new `regexp` and `keyword` rules is discouraged because it is easy to use them incorrectly, and proxy software cannot efficiently match these types of rules.
|
||||
|
||||
> [!NOTE]
|
||||
> The following types of rules are **NOT** fully compatible with the ones that defined by user in V2Ray config file. Do **Not** copy and paste directly.
|
||||
> The following types of rules are **NOT** fully compatible with the ones that defined by user in V2Ray config file. Do **NOT** 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.
|
||||
- Subdomain begins with `domain:`, followed by a valid domain name. The prefix `domain:` may be omitted.
|
||||
@@ -114,7 +116,7 @@ regexp:^odd[1-7]\.example\.org(\.[a-z]{2})?$
|
||||
- Regular expression begins with `regexp:`, followed by a valid regular expression (per Golang's standard).
|
||||
- Domain rules (including `domain`, `full`, `keyword`, and `regexp`) may have none, one or more attributes. Each attribute begins with `@` and followed by the name of the attribute. Attributes will remain available in final lists and `dlc.dat`.
|
||||
- Domain rules may have none, one or more affiliations, which additionally adds the domain rule into the affiliated target list. Each affiliation begins with `&` and followed by the name of the target list (nomatter whether the target has a dedicated file in data path). This is a method for data management, and will not remain in the final lists or `dlc.dat`.
|
||||
- Inclusion begins with `include:`, followed by the name of another valid domain list. A simple `include:listb` in file `lista` means adding all domain rules of `listb` into `lista`. Inclusions with attributes stands for selective inclusion. `include:listb @attr1 @-attr2` means only adding those domain rules *with* `@attr1` **and** *without* `@attr2`. This is a special type for data management, and will not remain in the final lists or `dlc.dat`.
|
||||
- Inclusion begins with `include:`, followed by the name of another valid domain list. `include:listb` in file `lista` means adding all domain rules of `listb` into `lista`. Inclusions with attributes stand for selective inclusion. `include:listb @attr1 @-attr2` means only adding those domain rules *with* `@attr1` **and** *without* `@attr2`. This is a special type for data management, and will not remain in the final lists or `dlc.dat`.
|
||||
|
||||
## How it works
|
||||
|
||||
|
||||
@@ -1,4 +1,5 @@
|
||||
# Game
|
||||
bestdori.com
|
||||
colorfulstage.com
|
||||
|
||||
# Idol
|
||||
|
||||
@@ -153,4 +153,5 @@ wireshark.org
|
||||
x.org
|
||||
xposed.info
|
||||
yarnpkg.com
|
||||
ziglang.org
|
||||
zsh.org
|
||||
|
||||
@@ -17,11 +17,10 @@ bouffalolab.com
|
||||
cxmt.com
|
||||
|
||||
# 乐鑫信息科技
|
||||
#include:espressif
|
||||
esp8266.cn
|
||||
esp8266.com
|
||||
esp8266.com.cn
|
||||
espressif.cn
|
||||
espressif.com
|
||||
espressif.com.cn
|
||||
|
||||
# 华秋电子
|
||||
|
||||
@@ -11,6 +11,7 @@ include:okko
|
||||
include:wink
|
||||
24h.tv
|
||||
amediateka.ru
|
||||
beeline.tv
|
||||
ivi.ru
|
||||
premier.one
|
||||
smotreshka.tv
|
||||
|
||||
@@ -97,6 +97,7 @@ myexternalip.com
|
||||
myip.com
|
||||
myip.ms
|
||||
myip.ru
|
||||
myip.wtf
|
||||
myipaddress.com
|
||||
myiplookup.com
|
||||
mylocation.org
|
||||
@@ -134,6 +135,7 @@ full:checkip.amazonaws.com
|
||||
full:ipv4-check-perf.radar.cloudflare.com
|
||||
full:ipv6-check-perf.radar.cloudflare.com
|
||||
geoip.noc.gov.ru
|
||||
ip.hetzner.com
|
||||
ip.mail.ru
|
||||
ip.nic.ru
|
||||
ip.tyk.nu
|
||||
|
||||
@@ -1625,3 +1625,6 @@ ao-x.ac.cn
|
||||
|
||||
# 万集科技 京ICP备18036282号-2
|
||||
wanji.net.cn
|
||||
|
||||
# 广州市雅望互联网服务有限公司
|
||||
gzyowin.com
|
||||
|
||||
30
data/qcloud
30
data/qcloud
@@ -258,13 +258,14 @@ tdnsv14.net
|
||||
tdnsv15.net
|
||||
|
||||
# myqcloud inside mainland China
|
||||
regexp:\.(.+-)?ap-beijing(-.+)?\.myqcloud\.com$ #北京
|
||||
regexp:\.(.+-)?ap-nanjing(-.+)?\.myqcloud\.com$ #南京
|
||||
regexp:\.(.+-)?ap-shanghai(-.+)?\.myqcloud\.com$ #上海
|
||||
regexp:\.(.+-)?ap-guangzhou(-.+)?\.myqcloud\.com$ #广州
|
||||
regexp:\.(.+-)?ap-chengdu(-.+)?\.myqcloud\.com$ #成都
|
||||
regexp:\.(.+-)?ap-chongqing(-.+)?\.myqcloud\.com$ #重庆
|
||||
regexp:\.(.+-)?ap-shenzhen(-.+)?\.myqcloud\.com$ #深圳
|
||||
# overrided by myqcloud.com
|
||||
#regexp:\.(.+-)?ap-beijing(-.+)?\.myqcloud\.com$ #北京
|
||||
#regexp:\.(.+-)?ap-nanjing(-.+)?\.myqcloud\.com$ #南京
|
||||
#regexp:\.(.+-)?ap-shanghai(-.+)?\.myqcloud\.com$ #上海
|
||||
#regexp:\.(.+-)?ap-guangzhou(-.+)?\.myqcloud\.com$ #广州
|
||||
#regexp:\.(.+-)?ap-chengdu(-.+)?\.myqcloud\.com$ #成都
|
||||
#regexp:\.(.+-)?ap-chongqing(-.+)?\.myqcloud\.com$ #重庆
|
||||
#regexp:\.(.+-)?ap-shenzhen(-.+)?\.myqcloud\.com$ #深圳
|
||||
|
||||
# COS 使用到的非中国大陆的地域与可用区,参见 https://cloud.tencent.com/document/product/436/6224
|
||||
ap-hongkong.myqcloud.com @!cn #中国香港
|
||||
@@ -282,13 +283,14 @@ eu-frankfurt.myqcloud.com @!cn #法兰克福
|
||||
eu-moscow.myqcloud.com @!cn #莫斯科
|
||||
|
||||
# tencentcos inside mainland China
|
||||
regexp:\.(.+-)?ap-beijing(-.+)?\.tencentcos\.(cn|com(\.cn)?)$ #北京
|
||||
regexp:\.(.+-)?ap-nanjing(-.+)?\.tencentcos\.(cn|com(\.cn)?)$ #南京
|
||||
regexp:\.(.+-)?ap-shanghai(-.+)?\.tencentcos\.(cn|com(\.cn)?)$ #上海
|
||||
regexp:\.(.+-)?ap-guangzhou(-.+)?\.tencentcos\.(cn|com(\.cn)?)$ #广州
|
||||
regexp:\.(.+-)?ap-chengdu(-.+)?\.tencentcos\.(cn|com(\.cn)?)$ #成都
|
||||
regexp:\.(.+-)?ap-chongqing(-.+)?\.tencentcos\.(cn|com(\.cn)?)$ #重庆
|
||||
regexp:\.(.+-)?ap-shenzhen(-.+)?\.tencentcos\.(cn|com(\.cn)?)$ #深圳
|
||||
# overrided by tencentcos.cn, tencentcos.com, tencentcos.com.cn
|
||||
#regexp:\.(.+-)?ap-beijing(-.+)?\.tencentcos\.(cn|com(\.cn)?)$ #北京
|
||||
#regexp:\.(.+-)?ap-nanjing(-.+)?\.tencentcos\.(cn|com(\.cn)?)$ #南京
|
||||
#regexp:\.(.+-)?ap-shanghai(-.+)?\.tencentcos\.(cn|com(\.cn)?)$ #上海
|
||||
#regexp:\.(.+-)?ap-guangzhou(-.+)?\.tencentcos\.(cn|com(\.cn)?)$ #广州
|
||||
#regexp:\.(.+-)?ap-chengdu(-.+)?\.tencentcos\.(cn|com(\.cn)?)$ #成都
|
||||
#regexp:\.(.+-)?ap-chongqing(-.+)?\.tencentcos\.(cn|com(\.cn)?)$ #重庆
|
||||
#regexp:\.(.+-)?ap-shenzhen(-.+)?\.tencentcos\.(cn|com(\.cn)?)$ #深圳
|
||||
|
||||
# tencentcos outside mainland China
|
||||
# regexp:.+\.ap-hongkong\.tencentcos\.(cn|com(\.cn)?)$ @!cn #中国香港
|
||||
|
||||
Reference in New Issue
Block a user