Pynqr
VANTH Studio / Guides / Ping, route and DNS
Troubleshooting

Ping, Traceroute and DNS Lookup on iPhone

These tools answer different questions. Used in the right order, they help separate device reachability, name resolution and route problems.

6-minute readReviewed August 10, 2026
Quick answerUse DNS lookup to check whether a name resolves, ping to test reachability and latency, and traceroute to observe the path toward a destination. A timeout is not always proof of failure because networks may deliberately ignore diagnostic traffic.

Choose the tool by the symptom

ToolQuestionUseful output
DNS lookupDoes this hostname resolve?Address records and lookup errors
PingDoes the host respond, and how long does it take?Latency, response variation, packet loss
TracerouteWhere does the path stop or slow down?Intermediate hops and response times

A simple diagnostic sequence

  1. Test the destination by name and note whether DNS returns an address.
  2. Test a known IP address to separate name resolution from connectivity.
  3. Ping the local router to check the immediate WiFi/LAN path.
  4. Ping a remote destination to compare local and internet behavior.
  5. Run traceroute when the local path works but the remote path remains unclear.
  6. Repeat measurements before drawing conclusions from one temporary spike.

How to read ping results

Round-trip time is the elapsed time for a request and response. Stable low latency to the router suggests the immediate local path is healthy. Variable local latency may point to weak WiFi, congestion or a busy device. Remote latency also includes the ISP and internet path.

Packet loss requires context. Some hosts rate-limit or ignore diagnostics while their normal application service still works. Test the service itself before declaring an outage.

How to read traceroute

Each hop is a router that chooses to return a diagnostic response. Missing hops in the middle are common and do not necessarily indicate a break. Focus on where loss or latency begins and whether it continues to later hops. A slow response from one intermediate router followed by normal later hops often reflects response prioritization, not forwarding performance.

How to read DNS results

If a hostname fails but its known IP works, investigate the configured DNS resolver, record type and spelling. Different record types serve different purposes: A and AAAA point to IPv4 and IPv6 addresses, MX handles mail, and TXT carries arbitrary policy or verification data.

Capture the conditionsRecord the WiFi name, time, destination and whether a VPN was active. VPNs, private relay features and split DNS can legitimately change the path and answer.

Related guides

Inspect IPs and ports · Choose the right scanner · See local devices

Keep the core tools together

Pynqr includes ping, traceroute and DNS lookup alongside device discovery.

Download Pynqr