Replies: 3 comments 1 reply
-
So long as the proxy's IP is listed in the #5768 might prove to have valuable information if that doesn't work. |
Beta Was this translation helpful? Give feedback.
-
Apifox or postman maybe work it |
Beta Was this translation helpful? Give feedback.
-
I was able to use the examples here. You have to manually encode/decode the request/response. In AdGuard Home, the client is displayed as the ClientID portion of the request url (/dns-query/ClientID/dns=). If you click on the ClientID, you can see the actual client hostname and IP (X-Real-IP works as override). Functionally, it serves my purpose. Visually, I would prefer to see the hostname and IP in the primary view. |
Beta Was this translation helpful? Give feedback.
-
The following curl command works for the public Cloudflare servers:
curl -H "accept: application/dns-json" "https://cloudflare-dns.com/dns-query?name=example.com&type=A"
Is there something similar I can use to test AdGuard Home? I've got https_dns_proxy talking to AGH and I can generate a ClientID from the URL suffix. I want to see if I can also pass in an X-Real-IP header.
[trusted_proxies If a DNS-over-HTTPS request comes from one of these addresses or networks, AdGuard Home uses the provided proxy headers, such as X-Real-IP, to get the real IP address of the client... ]
Beta Was this translation helpful? Give feedback.
All reactions