Unverified50% confidenceFactExact time
When the client is behind a forward proxy, the address resolved by local DNS may be unreachable, while what actually connects is the proxy-side resolution result, so continuing to pin the locally resolved IP would cause the request to point to an unreachable path.
1
Sources
50%
Confidence
Long-term
Relevance
10/16/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedWhen using a VPN or proxy, the IP lookup result will point to the physical location of the server, which is unrelated to the user's actual location.77% similarUnverifiedThe source of repeated failed requests can be located by examining nextcloud.log or the admin backend security log; if the source shows as localhost or a LAN IP, it is essentially a local client issue rather than an external attack67% similarUnverifiedNearly all network environments allow DNS query traffic to pass through, making it susceptible to abuse as a channel for data exfiltration or command delivery.66% similarUnverifiedDNS rebinding attacks exploit the flexibility of the TTL mechanism in the DNS protocol to bypass browser same-origin policies based on domain names by rapidly switching domain name resolution.66% similarUnverifiedEven when a container's default gateway is pointed to an internal DNS resolver, an agent that can directly construct UDP packets (via raw sockets or low-level network APIs) may still be able to bypass system-level DNS settings and connect directly to external authoritative servers.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1049573API
curl https://kongchang.com/api/v1/knowledge/claims/1049573MCP
get_claim(id=1049573)