Service eligibility and regional restrictions
PuppyIP serves only compliant overseas businesses and their authorized personnel. Proxy services are not available in mainland China. The service may only be used for lawful business activities outside mainland China. Use of this service within mainland China is prohibited.
Hosting a proxy IP or server overseas does not change these restrictions. The service must not be provided to end users in mainland China through relaying, forwarding, sharing or resale. Before use, read the Terms of Service.
Key Takeaways
- Investigate entry resolution when a -1 test result coincides with a failed real request; one latency value alone does not show that the node is unavailable.
- Read Windows system resolution, cache, a specified DNS query, and the client's actual entry path. The client core may use its own resolver.
- If the entry hostname fails, a temporary IP substitution succeeds, and restoring the hostname fails again under the same configuration, the A/B/A result shows only that this test was related to address selection. The GUI test and exact resolution path still need separate confirmation.
- Do not pin the temporary IP in hosts or persistent settings. Any lasting change requires checking address rotation, TLS names, and rollback.
Separate the test result from a real connection failure
If Windows v2rayN shows -1 and a real proxy request through the node also fails, checking entry-name resolution is one possible diagnostic layer. If the real request succeeds, -1 may still be limited to the test. Record TUN state, active core, current entry hostname, and real request error before deciding whether to query system DNS.
A latency test and an application request may use different connection paths. Determine whether the failure occurs at the entry connection, protocol handshake, or destination request. If the active core has its own DNS resolver, Windows resolution may not represent what the core actually used.
Read Windows system resolution and cache
On the affected PC, query the entry hostname's A record and the DNS client cache, noting the time and status. If you compare a specific DNS server, send the same name and record type to that resolver. A specified query is only a comparison; it does not change Windows DNS settings. Do not clear the cache or edit hosts to manufacture a new test condition.
PowerShell output below may include the real entry IP and DNS server. Do not paste it into a public ticket. Keep only whether resolution succeeded, whether an answer was present, and the TTL category; remove the actual name and address.
Read the entry hostname and local DNS cache
powershell$NODE_ENTRY = 'REPLACE_WITH_NODE_ENTRY_DOMAIN'
Resolve-DnsName -Name $NODE_ENTRY -Type A -DnsOnly
Get-DnsClientCache | Where-Object { $_.Entry -eq $NODE_ENTRY } | Select-Object Entry,Type,Status,Data,TimeToLive
Compare another DNS resolver only when appropriate
If the system query looks unusual and the environment permits it, run one specified DNS query for the same entry name. Keep the query type and time consistent, and note that a different resolver may return a different address. An answer from another DNS service or browser DoH describes only that query path; it does not prove that v2rayN/Xray used the same path.
Do not send queries to an arbitrary DNS service in an environment where you are not authorized to do so. Do not assume that one returned address is a stable node IP. The hostname may rotate, use multiple entries, or depend on a TLS name in the configuration; confirm those conditions separately.
Read the entry answer from an authorized DNS resolver
powershell$NODE_ENTRY = 'REPLACE_WITH_NODE_ENTRY_DOMAIN'
$DNS_SERVER = 'REPLACE_WITH_AUTHORIZED_DNS_SERVER'
Resolve-DnsName -Name $NODE_ENTRY -Type A -Server $DNS_SERVER -DnsOnly
Keep an IP substitution within a diagnostic A/B/A test
For an A/B/A diagnostic, keep the client config, core, network and target the same: test the original entry hostname, temporarily substitute its current resolved IP, then restore the hostname and test again. If the results are fail, succeed, fail, they show only that this test was related to entry-address selection. They do not establish Windows system DNS as the root cause; the substitution may also change client resolution, routing or server-name handling.
To repeat the comparison, record the original entry in the client session, make one temporary substitution, and restore it immediately afterward. Do not change hosts, persist the IP, remove the hostname, or also switch nodes, DNS, TLS name, port, or core.
Verify the active core's real request path
Use the same v2rayN configuration, core, destination, and network for every A/B step. Check whether the request completes and whether the core logs a matching connection. A system DNS query, cache entry, DoH page, and proxy application request are different indicators; only the actual proxy request shows whether the client connected this time.
If hostname resolution succeeds but the proxy request still fails, continue with the entry connection and protocol handshake. If an IP works but restoring the hostname fails, retain that temporary result and gather more evidence about the resolution path. Do not put the real entry hostname, IP-and-port combination, or raw core log in a public report.
Version scope, persistent changes, and unknowns
With Windows, v2rayN 7.22.4, Xray 26.3.27, and TUN off, use A/B/A only as a temporary comparison: if the hostname fails, a temporary IP works, and restoring the hostname fails again, record only that address substitution was related to this test. Do not persist the IP. The GUI test and exact resolution path still need separate confirmation.
This is a layered diagnostic and temporary comparison, not a fixed-IP repair guide. Before making a persistent DNS, DoH, or hosts change, obtain clear resolution evidence, confirm that the setting affects only the intended traffic, and record the original value and rollback steps.
Sources
Frequently Asked Questions
Does -1 mean the node entry hostname failed to resolve?
Not necessarily. Check a real request and keep the test target separate from the application connection path.
If a specified DNS resolves the name, does that prove v2rayN uses the same answer?
No. The client core may use a separate resolution path.
Can I pin the IP in hosts after the temporary test works?
Do not do that automatically. Confirm address stability, TLS name, and scope; the comparison did not prove a persistent root cause.
Can an A/B/A comparison establish a permanent repair?
No. If the hostname fails, a temporary IP works, and restoring the hostname fails again, the result only narrows this test to an address-selection-related path. Check client resolution, routing, and server-name handling, and verify the GUI test separately. Do not persist the IP before establishing the cause and a rollback plan.