Star Brilliant

> The same applies to the `received server failure from upstream` messages. `servfail` is pretty common in production, there's no need to log it by default, or at least there...

I am really sorry. I apologize for my rudeness. I was studying for an exam and suddenly received the update from this repo, so I didn't spend too much time...

I guess it's now fixed? Please reopen if you disagree.

IETF and Google are totally two different protocols. If dnsmasq only supports one protocol, you should only use that protocol. Furthermore, uploading your configuration file and detailed log (enable `verbose`)...

I can reproduce your results. Here is my conclusion: 1. NextDNS supports both IETF and Google mode. Both mode should work. 2. The “Record data contains newline” message is actually...

Thank you for your report! Actually this is an old problem. But since I found a good DoH server also requires OCSP Stapling, which I can not provide in a...

> You are of course right with OCSP Stapling, which still would not be solved. I tried to search an easy OCSP Stapling library for Go, but come up with...

> I guess this could be done after [golang/go#40017](https://github.com/golang/go/issues/40017)? This doesn't seem enough. We need to get `net/http.HTTPServer` to support OCSP stapling.

Go modify json-dns/globalip.go. There is no option on this, because I don't think there is a need to toggle this. For those users like you who know what they are...

I believe this is a problem with your upstream ad blocker. It should also replace `AAAA` record with `::` in addition to `A`. This problem would also affect users that...