Search Again: Testing performance of local DNS lookups From: Scott Haneda Date: Tuesday, October 26, 2004 Time: 10:56:10 pm And my saga continues... Forever I have had my DNS servers IP listed in my tcp/ip settings, this has served me well for ages now. After experiencing some DNS issues, I decided to enter in comcasts DNS servers in my tcp/ip settings. It is like a whole new web experience. Where I was used to a certain delay in resolving a domain name before Safari would display it, now it is immediate. How can I test where this bottleneck is happening? So far, I have done this: Dig somedomain.com @my.ip.address Dig somedomain.com @comcast.dns.ip.address Both results come back in about the same ms time range, give or take 1-5 ms's. Is this the proper way to test this, these results seem to lead me to think that I should have the same experience on both ip addresses, which is certainly not the case. Maybe I have been going about this all wrong, and should not have used my own DNS server for my lookups and should use that of the provider that is giving me my internet? I just find it hard to believe that with as many people as comcast has on the system, that little old me can not have a faster DNS server than them considering load. I really don't want to use another NS than mine anyway, since I want to see the edits I made to DNS right away, which helps me in development and the like. -- ------------------------------------------------------------- Scott Haneda Tel: 415.898.2602 <http://www.newgeo.com> Fax: 313.557.5052 <scott@newgeo.com> Novato, CA U.S.A.

Messages In This Thread: Testing performance of local DNS lookups by Scott Haneda on Oct 26, 2004 at 10:56:10 pm Re: Testing performance of local DNS lookups by admin@gippy.net on Oct 27, 2004 at 7:28:16 am