Folks,

Why does my dkim-filter make and keep open so many connecting to my upstream
DNS?

I found over 150 connections that look like this in netstat -anp:

udp        0      0 69.94.104.180:43052         <upstream DNS #1>:53
ESTABLISHED 3889/dkim-filter

And over 30 connections that look like this in netstat -anp:

udp        0      0 69.94.104.180:43052         <upstream DNS #2>:53
ESTABLISHED 3889/dkim-filter


And only one like this:

udp        0      0 127.0.0.1:59116             127.0.0.1:53
ESTABLISHED 3889/dkim-filter

I restarted dkim-filter and they all went away.  They don't come back right
away.  I assume that dkim-filter is connecting to the second nameserver in
my /etc/resolv.conf file when the first nameserver is not available.  I
don't understand why it opens so many connections over a period of weeks and
leaves them open.

My resolver configuration is:

# more /etc/resolv.conf
nameserver 127.0.0.1
nameserver <upstream DNS #1>
nameserver <upstream DNS #2>

I am running BIND 9.5.0-P1 as a caching nameserver:

#more  /etc/named.conf

options {
        directory "/var/named";
        allow-recursion { 127.0.0.1; 69.94.104.180; };
        listen-on { 127.0.0.1; 69.94.104.180; };
        transfer-source 69.94.104.180;
        transfers-out 300 ;
        pid-file "/var/run/named/named.pid";
};

Thanks for the help.

Jim
-----
Jim Hermann <[EMAIL PROTECTED]>
UUism Networks <http://www.UUism.net>
Ministering to the Needs of Online UUs
Web Hosting, Email Services, Mailing Lists
-----


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
dkim-milter-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dkim-milter-discuss

Reply via email to