You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If /32 (IPv4) or /128 (IPv6) address is specified in the ECS extension, we might want to use it instead of client address in the query log and stats modules.
In this case, we will be able to chain DNS queries keeping information about the actual client. For instance, from a local AdGuard Home or dnsproxy to a remote AdGuard Home instance located on a VPS.
The text was updated successfully, but these errors were encountered:
Here's the thread that gave me this idea:
AdguardTeam/dnsproxy#7
If
/32
(IPv4) or/128
(IPv6) address is specified in the ECS extension, we might want to use it instead of client address in the query log and stats modules.In this case, we will be able to chain DNS queries keeping information about the actual client. For instance, from a local AdGuard Home or
dnsproxy
to a remote AdGuard Home instance located on a VPS.The text was updated successfully, but these errors were encountered: