Get short, timely messages from Beverly Fischer.

Twitter is a rich source of instantly updated information. It's easy to stay updated on an incredibly wide variety of topics. Join today and follow @DNSComparison.

Get updates via SMS by texting follow DNSComparison to 40404 in the United States
Codes for other countries

Two-way (sending and receiving) short codes:
Country Code For customers of
Australia
  • 0198089488 Telstra
Canada
  • 21212 (any)
United Kingdom
  • 86444 Vodafone, Orange, 3, O2
Indonesia
  • 89887 AXIS, 3, Telkomsel
Ireland
  • 51210 O2
India
  • 53000 Bharti Airtel, Videocon
Jordan
  • 90903 Zain
New Zealand
  • 8987 Vodafone, Telecom NZ
United States
  • 40404 (any)

DNSComparison

  1. @dnsbrian Perhaps we can ask @Pingdom to generate a report for a few days for ns1,2,3,4.dns.com and post the reports publicly. That OK?
  2. @dnsbrian Agree that ur results should not b different than ours, but based on the routing of ur namesevers.Do not see how yours is possible
  3. @dnsbrian To average a low 30 ms for DNS queries you would need to keep all of your queries regional (at least in the same continent).
  4. @dnsbrian As the traceroutes from Level3, GBLX, NTT, Sprint, Tata all show the queries are not staying in the same region / continent.
  5. @dnsbrian Even DNSStuff http://bit.ly/iU8X5b is showing queries going across country. An electron only moves so fast.
  6. @dnsbrian That is very strange how you are seeing these low 30 ms numbers for the DNS.com name servers. The queries need to stay regionally
  7. @dnsbrian You can use the Looking Glass tools from the Tier1 bandwidth providers to see the DNS.com results we did from our traceroutes.
  8. @dnsbrian Here you go. http://bit.ly/mQpi01 Hope it helps your networking team out.
  9. @dnsbrian That may help your network team troubleshoot why our Pingdom results are higher than what you are expecting.
  10. @dnsbrian Would you like us to post traceroutes to your dns.com name servers going to different continents?
  11. @dnsbrian Just looked at your Pingdom graphs some more... not sure how that is possible (the values you are getting).
  12. @dnsbrian Are you only checking a certain city?
  13. @dnsbrian Very interesting how your results are 3x faster than what Pingdom is showing us. Are you certain you're checking the right system?
  14. @dnsbrian @dnscom Here's what we're seeing for March: http://bit.ly/jvQrIW
  15. @dnsbrian We will make a public page that shows the speed of all four of the Comwired/DNS.com nameservers to show you what Pingdom shows us.
  16. @dnsbrian The speeds were reported by Pingdom in March. All listed speeds are representative of the period noted at the top of the page.
  17. Due to circumstances beyond our control, this month's update will not post until Monday. Sorry for any inconvenience.
  18. Hello there March. Looks like it's time to get our update in order. Keep an eye on us for our first monthly update in the following days.
  19. Check in during the first week of the month to see how these managed services stack up.