make independant apple relay conf; add netease DNS mapping #62
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| # $ meta_title Sukka's Ruleset - Apple Relay | ||
| # $ meta_description This file contains domains for Apple Relay, hosted by Apple, Inc. | ||
|
|
||
| # >> Apple Relay | ||
| DOMAIN-SUFFIX,apple-relay.fastly-edge.com | ||
| DOMAIN-SUFFIX,apple-relay.cloudflare.com | ||
| DOMAIN-SUFFIX,apple-relay.apple.com | ||
| DOMAIN-SUFFIX,cp2.cloudflare.com | ||
| DOMAIN-SUFFIX,cp3.cloudflare.com | ||
| DOMAIN-SUFFIX,cp4.cloudflare.com | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -341,6 +341,41 @@ export const DOMESTICS: Record<string, DNSMapping> = { | |
| 'baomitu.com', | ||
| 'qiku.com' | ||
| ] | ||
| }, | ||
| NETEASE: { | ||
| hosts: {}, | ||
| dns: 'https://doh.pub/dns-query', | ||
| realip: false, | ||
| ruleset: true, | ||
| domains: [ | ||
| '126.com', | ||
| '126.net', | ||
| '127.com', | ||
| '127.net', | ||
| '+163.com', | ||
| '163yun.com', | ||
| '+163.com.cn', | ||
| '163jiasu.com', | ||
| '166.com', | ||
| '166.net', | ||
| '188.com', | ||
| 'netease.com', | ||
| '+neteasecloudmusic.com', | ||
| '+neteasegame.com', | ||
| '+netease.im', | ||
| 'netstatic.net', | ||
| 'lofter.com', | ||
| 'yeah.net', | ||
| 'ydstatic.com', | ||
| 'youdao.com', | ||
| 'youdao.cn', | ||
| 'yoozoo.com', | ||
| 'yqkk.link', | ||
| 'haowu.link', | ||
| 'laiqukankan.com', | ||
| 'zhuanzfx.com', | ||
| '321fenx.com' | ||
| ] | ||
|
Comment on lines
+345
to
+378
There was a problem hiding this comment. Why DNSPod? NetEase uses multiple CDNs from different providers. For instance, NetEase Music primarily uses Alibaba Cloud CDN. There was a problem hiding this comment.
I have never expected that. I didn't found public records saying NetEase have used multiple CDNs for different services.
I wrote the update from this record. There was a problem hiding this comment.
|
||
| } | ||
| }; | ||
|
|
||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not specifically for Apple. Many Cloudflare customers also use these domains.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://blog.cloudflare.com/stronger-than-a-promise-proving-oblivious-http-privacy-properties/
https://docs.fastly.com/products/oblivious-http-relay
The OHTTP Relay is designed to hide users' IP/Geolocation (and other PI & PII) from the service providers. Why do you need to specify a special policy to unlock those services?