I can not find any place in the app where it allows me to define the hosts I want to lookup. The hosts a home users looks up over the hosts AASP or any other MTA / proxy will be entirely different.
The below tests I just ran now, on my MTA, not saying at all your results are not better, but based on the posts on reddit about just the the other day, we call come to agreement, good for home use, bad for server user with google any-cast IP space being the closest for server use. You could be in open DNS geographic, heaven, for me, I an not get behind a company that has known bugs in their resolver and does nothing to fix them. First, these are all NON cachced results, since spam comes in waves, I am after the cachced results in this case. For is a quick file of misc zones: $cat zones a.b.c.foo.example.com abc.amazon.com amazon.com assp.sourceforge.net bl.spamcop.net google.com Here is my command for i in `cat zones`; do echo $i; dig $i @8.8.8.8 +norec | grep 'Query time'; echo "--"; done I change the @NS to 8.8.8.8 to mine, to oprnDNS, to 4.2.2.2 For each line listed in zones, run a dig on it, using ip's for google, openDNS, and myself. These are all run twice, with +norec Google: a.b.c.foo.example.com ;; Query time: 23 msec -- abc.amazon.com ;; Query time: 21 msec -- amazon.com ;; Query time: 23 msec -- assp.sourceforge.net ;; Query time: 22 msec -- bl.spamcop.net ;; Query time: 22 msec -- google.com ;; Query time: 24 msec -- bing.com ;; Query time: 22 msec OPenDNS: a.b.c.foo.example.com ;; Query time: 17 msec -- abc.amazon.com ;; Query time: 17 msec -- amazon.com ;; Query time: 18 msec -- assp.sourceforge.net ;; Query time: 18 msec -- bl.spamcop.net ;; Query time: 17 msec -- google.com ;; Query time: 21 msec -- bing.com ;; Query time: 20 msec -- My own NS: a.b.c.foo.example.com ;; Query time: 6 msec -- abc.amazon.com ;; Query time: 6 msec -- amazon.com ;; Query time: 9 msec -- assp.sourceforge.net ;; Query time: 7 msec -- bl.spamcop.net ;; Query time: 7 msec -- google.com ;; Query time: 7 msec -- bing.com ;; Query time: 7 msec -- The good old 4.2.2.2. that has been around a long time before google or openDNS, these were not cached, amazing.... a.b.c.foo.example.com ;; Query time: 6 msec -- abc.amazon.com ;; Query time: 6 msec -- amazon.com ;; Query time: 6 msec -- assp.sourceforge.net ;; Query time: 6 msec -- bl.spamcop.net ;; Query time: 7 msec -- google.com ;; Query time: 6 msec -- bing.com ;; Query time: 6 msec -- Just too see how crappy comcast is, though I would give them a shot: a.b.c.foo.example.com ;; Query time: 83 msec -- abc.amazon.com ;; Query time: 83 msec -- amazon.com ;; Query time: 82 msec -- assp.sourceforge.net ;; Query time: 83 msec -- bl.spamcop.net ;; Query time: 83 msec -- google.com ;; Query time: 83 msec -- bing.com ;; Query time: 83 msec -- I ran them multiple times, these are good averages... For me, the way I have my DNS setup, and how I have local WL and BL zones, rbldnsd zones, etc, and how much faster my local lookups are, and how much more accurate they are to me at at the time, for now, I am staying with my sub 8 second results, or, moving back to 4.2.2.2 Thanks for the input. -- Scott * If you contact me off list replace talklists@ with scott@ * On Dec 6, 2009, at 11:22 PM, Fritz Borgstedt wrote: > The topic here is the use of the DNS Benchmarck Utility. Try it and > then argue. ------------------------------------------------------------------------------ Join us December 9, 2009 for the Red Hat Virtual Experience, a free event focused on virtualization and cloud computing. Attend in-depth sessions from your desk. Your couch. Anywhere. http://p.sf.net/sfu/redhat-sfdev2dev _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
