RE: Arlib ResolverTracing on opendkim-2.3.1 shows identical queries

From: Murray S. Kucherawy <msk_at_cloudmark.com>
Date: Wed, 30 Mar 2011 07:53:37 -0700

> -----Original Message-----
> From: opendkim-dev-bounce_at_lists.opendkim.org [mailto:opendkim-dev-bounce_at_lists.opendkim.org] On Behalf Of Andreas Schulze
> Sent: Wednesday, March 30, 2011 7:16 AM
> To: Gary Mills
> Cc: opendkim-dev_at_lists.opendkim.org
> Subject: Re: Arlib ResolverTracing on opendkim-2.3.1 shows identical
> queries
>
> maybe the three queries are going to 3 nameservers:
>
> # dig umanitoba.ca ns +short
> zaurak.cc.umanitoba.ca.
> eceserver.ee.umanitoba.ca.
> clyde.concordia.ca.

No, there are no parallel redundant queries sent.

> A general question:
> *Why* does opendkim not simply ask the resolver configured in
> /etc/resolv.conf?
> On my systems this is always an unbound_at_127.0.0.1. That shouldn't be much slower
> then libunbound inside opendkim itself.

The nameservers are pulled from /etc/resolv.conf for all three resolver options.
Received on Wed Mar 30 2011 - 14:53:45 PST