Purpose Of The Ping Tool
The Hub Ping tool sends a bounded ICMP ping from the Public DC Hublist server to a public hub hostname or IP address. It is useful for quick reachability checks, DNS-change verification, and comparing what the hublist server can reach with what your own computer can reach.
Fields And Controls
- Host Or Address: Enter a public hostname, IP address, or hub-style URL such as
dchub://example.com:411. The tool extracts the public host and blocks private, local, reserved, and malformed targets. - Run Ping: Starts the check with a secure form token. Non-admin visitors may need CAPTCHA when it is enabled.
- Help Icon: Opens this article without losing the current form.
Reading The Results
The result shows resolved addresses, packets sent, packets received, packet loss, minimum/average/maximum latency, and bounded raw command output. Low latency and no packet loss usually mean the host is reachable from the hublist server. Packet loss, timeout, or DNS failure means more checks are needed.
Common Errors
- DNS Failed: The hostname did not resolve. Check spelling, nameservers, TTL, and whether the domain expired.
- 100% Packet Loss: ICMP may be blocked by the host, firewall, VPS provider, or upstream network. The hub can still work if its TCP port is open.
- Private Target Blocked: The tool rejects LAN, loopback, multicast, and reserved addresses to prevent abuse.
- High Latency: Routing may be long, congested, or filtered. Compare with traceroute and TCP connect results.
Best Follow-Up Checks
Ping alone does not prove that NMDC, NMDCS, ADC, or ADCS is working. If ping fails or looks suspicious, use the TCP Connect, Protocol Test, Port Scan, DNS, and Traceroute tools to check the actual hub service.