In this article

Use this article to investigate slow DNS responses or connectivity issues when resolving domains through DNSFilter.

DNSFilter operates a global Anycast network with hundreds of DNS servers across multiple data centers worldwide. In most environments, DNS queries resolve quickly and consistently. If slow responses are suspected, the issue is typically related to network routing between the environment and the DNSFilter network.

Common symptoms include

• DNS timeouts
• High round-trip time (RTT) or latency
• Packet loss during DNS queries

These issues are often caused by a suboptimal network route between the originating network and the DNSFilter resolvers. Collecting route diagnostics allows Support to compare the route from the network to DNSFilter and identify possible routing improvements.

Troubleshooting with MTR / WinMTR

MTR is the preferred diagnostic tool for identifying routing issues because it combines the functionality of ping and traceroute.

Windows

1. Download and open WinMTR
2. Enter one of the DNSFilter resolver IP addresses in the Host field:
   • 103.247.36.36
   • 103.247.37.37
3. Run the test for approximately 50 packets
4. Stop the test
5. Select Export TEXT and save the results

Run a separate test for each resolver IP address.

Send the exported results to Support as a .txt file or Ghostbin link. Avoid pasting results directly into the support ticket.

macOS

MTR must be installed using Homebrew or Xcode tools.

Run the following commands separately:

mtr -c50 -T --report 103.247.36.36
mtr -c50 -T --report 103.247.37.37

Save the output and provide the results as a .txt file or Ghostbin link.

Linux

Run the following commands separately:

mtr -c50 -T --report 103.247.36.36
mtr -c50 -T --report 103.247.37.37

Send the results to Support as a .txt file or Ghostbin link.

Troubleshooting with ping and traceroute

If MTR or WinMTR cannot be used, ping and traceroute commands can provide similar information.

Review the results for high latency, packet loss, or routing anomalies. If abnormalities are observed, provide the results to Support as a .txt file or Ghostbin link.

Windows

Run the following commands from Command Prompt:

tracert -w 100 103.247.36.36
tracert -w 100 103.247.37.37
ping -n 50 103.247.36.36
ping -n 50 103.247.37.37

macOS

Run the following commands from Terminal:

sudo traceroute -P TCP 103.247.36.36
sudo traceroute -P TCP 103.247.37.37
ping -qc 50 103.247.36.36
ping -qc 50 103.247.37.37

Linux

Run the following commands from the terminal or CLI:

sudo tcptraceroute 103.247.36.36
sudo tcptraceroute 103.247.37.37
ping -qc 50 103.247.36.36
ping -qc 50 103.247.37.37

Related troubleshooting

If DNS latency is not the root cause, the following articles may help identify other issues affecting website access:

• Websites are allowed by policy but do not load
• Specific websites are slow or fail to load
• Websites load without images or ads
• Websites fail to load on Apple devices