Star Brilliant

I prefer to close this issue because DNS filtering is generally done by another software. I personally want to include only features that must be implemented at DoH layer. (For...

Thank you for your contribution! I remember I once used net.ParseCIDR for this, but later I rewrote it without net.ParseCIDR. I forget the exact reason why net.ParseCIDR did not work....

The test fails with IPv4-mapped-IPv6 addresses: ``` parseIp("::ffff:7f00:1/0") parseIp("::ffff:7f00:1/120") parseIp("::ffff:7f00:1") parseIp("127.0.0.1/0") parseIp("127.0.0.1/24") parseIp("127.0.0.1") ``` `net.ParseCIDR` cannot distinguish between these two cases. And if we write additional logic to address this...

> The result of msg.Pack() is ok~ A recent pull does not pass the test. Please update your code to fix the problem.

This may be a bug. And the reason may be I never tested this against a client that didn't support DNSSEC. Have you tried the IETF protocol mode? That mode...

DoT and DoH are completely different protocols. Implementing DoT would require around 30% of work. However, I will not implement DoT by myself. The reason is simple: This protocol cannot...

> If you need the DoT and you are using Nginx as proxy is pretty simple, just add this in your nginx.conf file: Wow! So easy!

I think we can use the [`hash/fnv`](https://golang.org/pkg/hash/fnv/) package of the Go standard library. It provides the Fowler–Noll–Vo hash function, which is a fast algorithm for hash table use. I think...

Actually this is the exact problem I have observed on my lab environment in China. I have made various attempts through the years trying to fix this. But the HTTP/2.0...

The problem is: if a single HTTP/2.0 connection to the server fails, my code detects it and tries to start a new connection, but the Go standard library did not...