We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
All Ip's to the right are reported hijacked or incorrect. What does this mean? namebench 1.3.1 Shaw Vancouver-2 CA is 416.5% Faster than your current primary DNS server Recommended configuration (fastest + nearest) Primary Server 64.59.144.17 Shaw Vancouver-2 CA Secondary Server 64.59.144.92 Shaw Vancouver-3 CA Tertiary Server 208.67.220.220 OpenDNS Tested DNS Servers IP Descr. Hostname Avg (ms) Diff Min Max TO NX Notes 64.59.144.17 Shaw Vancouver-2 CA pd1nsc2.st.vc.shawcable.net 48.13 416.5% 11.4 549.2 0 0 www.google.com is hijacked: 173.194.33.148, 173.194.33.146, 173.194.33.145, 173.194.33.147, 173.194.33.144 google.com appears incorrect: 173.194.33.136, 173.194.33.135, 173.194.33.137, 173.194.33.129, 173.194.33.132, 173.194.33.134, 173.194.33.131, 173.194.33.130, 173.194.33.128, 173.194.33.142, 173.194.33.133 NXDOMAIN Hijacking (www) twitter.com appears incorrect: 199.16.156.38, 199.16.156.102, 199.16.156.6, 199.16.156.198 64.59.144.16 Shaw Vancouver CA pd1nsc1.st.vc.shawcable.net 57.06 335.8% 11.9 903.2 0 0 www.google.com is hijacked: 173.194.33.116, 173.194.33.113, 173.194.33.115, 173.194.33.112, 173.194.33.114 twitter.com appears incorrect: 199.16.156.70, 199.16.156.6, 199.16.156.102, 199.16.156.198 google.com appears incorrect: 173.194.33.96, 173.194.33.97, 173.194.33.102, 173.194.33.98, 173.194.33.110, 173.194.33.104, 173.194.33.100, 173.194.33.99, 173.194.33.101, 173.194.33.105, 173.194.33.103 8.8.4.4 Google Public DNS-2 google-public-dns-b.google.com 61.52 304.2% 21.9 566.6 0 0 Replica of Click! US [131.191.7.12] www.google.com is hijacked: 173.194.33.179, 173.194.33.180, 173.194.33.178, 173.194.33.176, 173.194.33.177 twitter.com appears incorrect: 199.59.149.230, 199.59.150.7, 199.59.150.39, 199.59.148.10 google.com appears incorrect: 173.194.33.4, 173.194.33.1, 173.194.33.2, 173.194.33.6, 173.194.33.9, 173.194.33.14, 173.194.33.0, 173.194.33.8, 173.194.33.3, 173.194.33.5, 173.194.33.7 64.59.144.92 Shaw Vancouver-3 CA pd2nsc3.st.vc.shawcable.net 64.49 285.5% 11.3 1767.1 0 0 NXDOMAIN Hijacking (www) www.google.com is hijacked: 173.194.33.80, 173.194.33.84, 173.194.33.82, 173.194.33.81, 173.194.33.83 google.com appears incorrect: 173.194.33.72, 173.194.33.66, 173.194.33.71, 173.194.33.70, 173.194.33.68, 173.194.33.69, 173.194.33.65, 173.194.33.73, 173.194.33.64, 173.194.33.67, 173.194.33.78 twitter.com appears incorrect: 199.16.156.102, 199.16.156.6, 199.16.156.198, 199.16.156.70 64.59.144.18 Shaw OR CA pd1nsc3.st.vc.shawcable.net 65.30 280.8% 12.8 1607.4 0 0 google.com appears incorrect: 173.194.33.174, 173.194.33.169, 173.194.33.163, 173.194.33.160, 173.194.33.162, 173.194.33.164, 173.194.33.165, 173.194.33.167, 173.194.33.161, 173.194.33.168, 173.194.33.166 twitter.com appears incorrect: 199.16.156.6, 199.16.156.230, 199.16.156.198, 199.16.156.102 NXDOMAIN Hijacking (www) www.google.com is hijacked: 173.194.33.179, 173.194.33.176, 173.194.33.177, 173.194.33.180, 173.194.33.178 208.67.220.220 OpenDNS resolver2.opendns.com 118.91 109.1% 11.7 683.5 0 0 google.com appears incorrect: 173.194.33.101, 173.194.33.103, 173.194.33.102, 173.194.33.96, 173.194.33.104, 173.194.33.105, 173.194.33.99, 173.194.33.98, 173.194.33.110, 173.194.33.100, 173.194.33.97 twitter.com appears incorrect: 199.59.150.39, 199.59.149.230, 199.59.148.10, 199.59.148.82 www.google.com is hijacked: 173.194.33.17, 173.194.33.16, 173.194.33.18, 173.194.33.19, 173.194.33.20 156.154.71.1 UltraDNS-2 rdns2.ultradns.net 179.09 38.8% 59.4 3285.9 0 0 twitter.com appears incorrect: 199.59.148.82, 199.59.149.198, 199.59.149.230, 199.59.150.7 NXDOMAIN Hijacking www.google.com is hijacked: 74.125.23.105, 74.125.23.106, 74.125.23.103, 74.125.23.147, 74.125.23.104, 74.125.23.99 213.5.182.117 SYS-213.5.182.117 213.5.182.117 248.62 148.2 1598.5 2 0 The current preferred DNS server. www.google.com is hijacked: 173.194.112.209, 173.194.112.212, 173.194.112.210, 173.194.112.208, 173.194.112.211 twitter.com appears incorrect: 199.16.156.6, 199.16.156.38, 199.16.156.230, 199.16.156.198 216.146.36.36 DynGuide-2 resolver2.dyndnsinternetguide.com 284.15 -12.5% 81.0 3500.0 6 0 www.google.com is hijacked: 74.125.224.212, 74.125.224.210, 74.125.224.208, 74.125.224.209, 74.125.224.211 NXDOMAIN Hijacking twitter.com appears incorrect: 199.59.148.10, 199.59.149.198, 199.59.150.7, 199.59.150.39 185.51.195.195 SYS-185.51.195.195 185.51.195.195 293.03 -15.2% 159.3 1418.5 0 0 A backup DNS server for this system. www.google.com is hijacked: 74.125.225.17, 74.125.225.19, 74.125.225.16, 74.125.225.18, 74.125.225.20 twitter.com appears incorrect: 199.16.156.6, 199.16.156.38, 199.16.156.70, 199.16.156.102 209.90.160.220 Priumus-2 CA radius2.primus.ca 321.36 -22.6% 13.6 3500.0 9 0 twitter.com appears incorrect: 199.16.156.6, 199.16.156.38, 199.16.156.70, 199.16.156.102 www.google.com is hijacked: 74.125.225.20, 74.125.225.17, 74.125.225.16, 74.125.225.19, 74.125.225.18 Graphs Mean Response Duration Mean Duration Graph Fastest Individual Response Duration Fastest Response Graph Response Distribution Chart (First 200ms) Response Distribution Graph (first 200ms) Response Distribution Chart (Full) Response Distribution Graph (full) Query Details View the details in Comma Separated Values (csv) format. Configuration Name Value benchmark_thread_count 2 enable_censorship_checks 0 health_thread_count 40 health_timeout 3.75 hide_results 0 input_source firefox num_servers 11 ping_timeout 0.5 query_count 250 run_count 1 select_mode automatic template html timeout 3.5 upload_results 0 version 1.3.1
Original issue reported on code.google.com by cosenza...@gmail.com on 11 Oct 2014 at 8:47
cosenza...@gmail.com
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Original issue reported on code.google.com by
cosenza...@gmail.com
on 11 Oct 2014 at 8:47The text was updated successfully, but these errors were encountered: