Andrey Meshkov
Andrey Meshkov
@Potterli20 you can change the port here before building dnsproxy: https://github.com/AdguardTeam/dnsproxy/blob/master/main.go#L294
If there's a leak we'll see it from that heap dump just okay.
Interesting approach with `ddr://` proto, I like it.
Could it be just a bug of private DNS implementation in Android?
AdGuard DNS blocks it the way that Apple recommends. If it does not work, this is probably on Apple. The only idea I suggest to check before reporting this: try...
https://developer.apple.com/support/prepare-your-network-for-icloud-private-relay/ ``` mask.icloud.com mask-h2.icloud.com ``` If these two domains cannot be resolved Apple Private Relay should stop working.
Let's keep it open, just in case anyone else would check it. I see no issues with this feature on our side, it works as expected and forces NXDOMAIN response...
Internal ID: AGDNS-1378
Internal ID: AGDNS-1377 Considering that protection status change is not real-time and may take 10 seconds or more, we should only provide rather large periods, starting with 5 minutes.
I don't see any automatic sync with cname-trackers here in the repo, it seems the files are synced manually from time to time? Then probably the false positive should be...