Closed kun-zhou closed 7 years ago
That's simply a DNS reverse proxy. When accessing any url, the devices always need to send an inquiry to the DNS server to get the IP address. This DNS will direct you to the proxy server rather than the server of netease while accessing specific URL. However, while accessing non-restricted website, the DNS will redirect your request to Google DNS and you will connect the website server directly. So no proxy will be detected.
Oh, I see. Thanks!
On Apr 26, 2017, at 11:08 AM, tommyzhaozbh notifications@github.com wrote:
That's simply a DNS reverse proxy. When accessing any url, the devices always need to send an inquiry to the DNS server to get the IP address. This DNS will direct you to the proxy server rather than the server of netease while accessing specific URL. However, while accessing non-restricted website, the DNS will redirect your request to Google DNS and you will connect the website server directly. So no proxy will be detected.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
I am wondering how does switching name server affects the accessibility of blocked contents? For instance, I live in the US, and after changing my DNS, my public IP did not change (as expected), but Netease Music seems to be allowing me to download stuff that was previously only intended for mainland users. Merely changing the DNS shouldn't matter assuming I get the same IP address for the domain names I am querying. But then why is it working?