Mailing List Archive

No DNS available
I'm getting this:

eval failed: available_nameservers: No DNS servers available!

I do have nameservers available, and Net::DNS is installed, so I'm a bit
stuck.

Any advice?
Thanks
Re: No DNS available [ In reply to ]
Walter,

> I'm getting this:
> eval failed: available_nameservers: No DNS servers available!
> I do have nameservers available, and Net::DNS is installed,
> so I'm a bit stuck.

Is the file /etc/resolv.conf readable by user running spamd?
Does it contain valid 'nameserver' entries?
Running spamd (or amavisd) in a chroot jail?

Are you using a directive dns_server or clear_dns_servers
in your .cf file check its validity.

Mark
Re: No DNS available [ In reply to ]
On Tue, 17 Jun 2014 13:16:07 +0200, Mark Martinec wrote:

> Walter,
>
>> I'm getting this:
>> eval failed: available_nameservers: No DNS servers available!
>> I do have nameservers available, and Net::DNS is installed,
>> so I'm a bit stuck.
>
> Is the file /etc/resolv.conf readable by user running spamd?
> Does it contain valid 'nameserver' entries?
> Running spamd (or amavisd) in a chroot jail?
>
> Are you using a directive dns_server or clear_dns_servers in your .cf
> file check its validity.
>
Thanks for the response. I'm actually not using spamc/spamd; just running
spamassassin from procmail. But anyway, /etc/resolv.conf is world
readable and contains valid nameserver entries.

No, I'm not running it in a chrooted environment of any kind.

There are no dns directive in my local.cf.

Any further thoughts?
Re: No DNS available [ In reply to ]
Walter,

> Thanks for the response. I'm actually not using spamc/spamd; just
> running
> spamassassin from procmail. But anyway, /etc/resolv.conf is world
> readable and contains valid nameserver entries.
>
> No, I'm not running it in a chrooted environment of any kind.
>
> There are no dns directive in my local.cf.
>
> Any further thoughts?

Try:

$ spamassassin -D dns -t <test.msg


Mark
Re: No DNS available [ In reply to ]
On Tue, 17 Jun 2014 16:08:52 +0200, Mark Martinec wrote:

> Walter,
>
>> Thanks for the response. I'm actually not using spamc/spamd; just
>> running spamassassin from procmail. But anyway, /etc/resolv.conf is
>> world readable and contains valid nameserver entries.
>>
>> No, I'm not running it in a chrooted environment of any kind.
>>
>> There are no dns directive in my local.cf.
>>
>> Any further thoughts?
>
> Try:
>
> $ spamassassin -D dns -t <test.msg
>
$ spamassassin -D dns -t < /usr/share/doc/spamassassin/sample-nonspam.txt
Jun 17 21:10:28.015 [832] dbg: dns: EDNS, UDP payload size 4096
Jun 17 21:10:28.016 [832] dbg: dns: servers obtained from Net::DNS :
Jun 17 21:10:28.016 [832] dbg: dns: eval failed: available_nameservers:
No DNS servers available!
Jun 17 21:10:28.016 [832] dbg: dns: using socket module: IO::Socket::IP
Jun 17 21:10:28.016 [832] dbg: dns: is Net::DNS::Resolver available? yes
Jun 17 21:10:28.017 [832] dbg: dns: Net::DNS version: 0.77
Jun 17 21:10:31.510 [832] dbg: dns: EDNS, UDP payload size 4096
Jun 17 21:10:31.510 [832] dbg: dns: servers obtained from Net::DNS :
Jun 17 21:10:31.511 [832] dbg: dns: eval failed: available_nameservers:
No DNS servers available!
Jun 17 21:10:31.511 [832] dbg: dns: using socket module: IO::Socket::IP
Jun 17 21:10:31.511 [832] dbg: dns: is Net::DNS::Resolver available? yes
Jun 17 21:10:31.511 [832] dbg: dns: Net::DNS version: 0.77
Jun 17 21:10:31.643 [832] dbg: dns: clear_resolver
Jun 17 21:10:31.645 [832] dbg: dns: EDNS, UDP payload size 4096
Jun 17 21:10:31.645 [832] dbg: dns: eval failed: available_nameservers:
No DNS servers available!
Jun 17 21:10:31.645 [832] dbg: dns: using socket module: IO::Socket::IP
Jun 17 21:10:31.645 [832] dbg: dns: is Net::DNS::Resolver available? yes
Jun 17 21:10:31.645 [832] dbg: dns: Net::DNS version: 0.77
Jun 17 21:10:31.645 [832] dbg: dns: dns_available set to yes in config
file, skipping test
Jun 17 21:10:31.679 [832] warn: plugin: eval failed:
available_nameservers: No DNS servers available!
Jun 17 21:10:31.680 [832] dbg: dns: checking RBL iadb.isipp.com., set
iadb-firsttrusted
Jun 17 21:10:31.681 [832] dbg: dns: IPs found: full-external:
199.172.62.20, 199.172.62.134, 199.172.62.5, 199.172.62.134,
199.172.62.5, 208.192.102.199 untrusted: 199.172.62.20, 199.172.62.134,
199.172.62.5, 208.192.102.199 originating:
Jun 17 21:10:31.681 [832] dbg: dns: only inspecting the following IPs:
199.172.62.20
Jun 17 21:10:31.682 [832] dbg: dns: checking RBL zen.spamhaus.org., set
zen
Jun 17 21:10:31.682 [832] dbg: dns: IPs found: full-external:
199.172.62.20, 199.172.62.134, 199.172.62.5, 199.172.62.134,
199.172.62.5, 208.192.102.199 untrusted: 199.172.62.20, 199.172.62.134,
199.172.62.5, 208.192.102.199 originating:
Jun 17 21:10:31.683 [832] dbg: dns: only inspecting the following IPs:
208.192.102.199, 199.172.62.5, 199.172.62.134, 199.172.62.20
Jun 17 21:10:31.684 [832] dbg: dns: checking RBL wl.mailspike.net., set
mspikeg-firsttrusted
Jun 17 21:10:31.685 [832] dbg: dns: IPs found: full-external:
199.172.62.20, 199.172.62.134, 199.172.62.5, 199.172.62.134,
199.172.62.5, 208.192.102.199 untrusted: 199.172.62.20, 199.172.62.134,
199.172.62.5, 208.192.102.199 originating:
Jun 17 21:10:31.685 [832] dbg: dns: only inspecting the following IPs:
199.172.62.20
Jun 17 21:10:31.686 [832] dbg: dns: checking RBL
bb.barracudacentral.org.,
set brbl-lastexternal
Jun 17 21:10:31.687 [832] dbg: dns: IPs found: full-external:
199.172.62.20, 199.172.62.134, 199.172.62.5, 199.172.62.134,
199.172.62.5, 208.192.102.199 untrusted: 199.172.62.20, 199.172.62.134,
199.172.62.5, 208.192.102.199 originating:
Jun 17 21:10:31.687 [832] dbg: dns: only inspecting the following IPs:
199.172.62.20
Jun 17 21:10:31.688 [832] dbg: dns: checking RBL dnsbl.sorbs.net., set
sorbs
Jun 17 21:10:31.688 [832] dbg: dns: IPs found: full-external:
199.172.62.20, 199.172.62.134, 199.172.62.5, 199.172.62.134,
199.172.62.5, 208.192.102.199 untrusted: 199.172.62.20, 199.172.62.134,
199.172.62.5, 208.192.102.199 originating:
Jun 17 21:10:31.689 [832] dbg: dns: only inspecting the following IPs:
208.192.102.199, 199.172.62.5, 199.172.62.134, 199.172.62.20
Jun 17 21:10:31.690 [832] dbg: dns: checking RBL sa-
trusted.bondedsender.org., set ssc-firsttrusted
Jun 17 21:10:31.690 [832] dbg: dns: IPs found: full-external:
199.172.62.20, 199.172.62.134, 199.172.62.5, 199.172.62.134,
199.172.62.5, 208.192.102.199 untrusted: 199.172.62.20, 199.172.62.134,
199.172.62.5, 208.192.102.199 originating:
Jun 17 21:10:31.690 [832] dbg: dns: only inspecting the following IPs:
199.172.62.20
Jun 17 21:10:31.692 [832] dbg: dns: checking RBL list.dnswl.org., set
dnswl-firsttrusted
Jun 17 21:10:31.692 [832] dbg: dns: IPs found: full-external:
199.172.62.20, 199.172.62.134, 199.172.62.5, 199.172.62.134,
199.172.62.5, 208.192.102.199 untrusted: 199.172.62.20, 199.172.62.134,
199.172.62.5, 208.192.102.199 originating:
Jun 17 21:10:31.692 [832] dbg: dns: only inspecting the following IPs:
199.172.62.20
Jun 17 21:10:31.693 [832] dbg: dns: checking RBL bl.mailspike.net., set
mspikeb-lastexternal
Jun 17 21:10:31.694 [832] dbg: dns: IPs found: full-external:
199.172.62.20, 199.172.62.134, 199.172.62.5, 199.172.62.134,
199.172.62.5, 208.192.102.199 untrusted: 199.172.62.20, 199.172.62.134,
199.172.62.5, 208.192.102.199 originating:
Jun 17 21:10:31.694 [832] dbg: dns: only inspecting the following IPs:
199.172.62.20
Jun 17 21:10:31.696 [832] dbg: dns: checking A and MX for host
world.std.com
Jun 17 21:10:31.697 [832] warn: rules: failed to run NO_DNS_FOR_FROM RBL
test, skipping:
Jun 17 21:10:31.697 [832] warn: (available_nameservers: [...] No DNS
servers available!)
Jun 17 21:10:31.698 [832] dbg: dns: checking RBL psbl.surriel.com., set
psbl-lastexternal
Jun 17 21:10:31.698 [832] dbg: dns: IPs found: full-external:
199.172.62.20, 199.172.62.134, 199.172.62.5, 199.172.62.134,
199.172.62.5, 208.192.102.199 untrusted: 199.172.62.20, 199.172.62.134,
199.172.62.5, 208.192.102.199 originating:
Jun 17 21:10:31.698 [832] dbg: dns: only inspecting the following IPs:
199.172.62.20
Jun 17 21:10:31.699 [832] dbg: dns: checking RBL dnsbl.sorbs.net., set
sorbs-lastexternal
Jun 17 21:10:31.699 [832] dbg: dns: IPs found: full-external:
199.172.62.20, 199.172.62.134, 199.172.62.5, 199.172.62.134,
199.172.62.5, 208.192.102.199 untrusted: 199.172.62.20, 199.172.62.134,
199.172.62.5, 208.192.102.199 originating:
Jun 17 21:10:31.700 [832] dbg: dns: only inspecting the following IPs:
199.172.62.20
Jun 17 21:10:31.701 [832] dbg: dns: checking RBL zen.spamhaus.org., set
zen-lastexternal
Jun 17 21:10:31.701 [832] dbg: dns: IPs found: full-external:
199.172.62.20, 199.172.62.134, 199.172.62.5, 199.172.62.134,
199.172.62.5, 208.192.102.199 untrusted: 199.172.62.20, 199.172.62.134,
199.172.62.5, 208.192.102.199 originating:
Jun 17 21:10:31.701 [832] dbg: dns: only inspecting the following IPs:
199.172.62.20
Jun 17 21:10:31.702 [832] dbg: dns: checking RBL sa-accredit.habeas.com.,
set ssc-firsttrusted
Jun 17 21:10:31.703 [832] dbg: dns: IPs found: full-external:
199.172.62.20, 199.172.62.134, 199.172.62.5, 199.172.62.134,
199.172.62.5, 208.192.102.199 untrusted: 199.172.62.20, 199.172.62.134,
199.172.62.5, 208.192.102.199 originating:
Jun 17 21:10:31.703 [832] dbg: dns: only inspecting the following IPs:
199.172.62.20
Jun 17 21:10:31.704 [832] dbg: dns: checking RBL
bl.score.senderscore.com., set rnbl-lastexternal
Jun 17 21:10:31.704 [832] dbg: dns: IPs found: full-external:
199.172.62.20, 199.172.62.134, 199.172.62.5, 199.172.62.134,
199.172.62.5, 208.192.102.199 untrusted: 199.172.62.20, 199.172.62.134,
199.172.62.5, 208.192.102.199 originating:
Jun 17 21:10:31.704 [832] dbg: dns: only inspecting the following IPs:
199.172.62.20
Jun 17 21:10:31.705 [832] dbg: dns: checking RBL zen.spamhaus.org., set
zen-lastexternal
Jun 17 21:10:31.706 [832] dbg: dns: IPs found: full-external:
199.172.62.20, 199.172.62.134, 199.172.62.5, 199.172.62.134,
199.172.62.5, 208.192.102.199 untrusted: 199.172.62.20, 199.172.62.134,
199.172.62.5, 208.192.102.199 originating:
Jun 17 21:10:31.706 [832] dbg: dns: only inspecting the following IPs:
199.172.62.20
Jun 17 21:10:31.707 [832] dbg: dns: checking RBL bl.spamcop.net., set
spamcop
Jun 17 21:10:31.707 [832] dbg: dns: IPs found: full-external:
199.172.62.20, 199.172.62.134, 199.172.62.5, 199.172.62.134,
199.172.62.5, 208.192.102.199 untrusted: 199.172.62.20, 199.172.62.134,
199.172.62.5, 208.192.102.199 originating:
Jun 17 21:10:31.707 [832] dbg: dns: only inspecting the following IPs:
208.192.102.199, 199.172.62.5, 199.172.62.134, 199.172.62.20
Jun 17 21:10:34.057 [832] warn: spf: lookup failed:
available_nameservers:
No DNS servers available!
Jun 17 21:10:34.064 [832] warn: spf: lookup failed:
available_nameservers:
No DNS servers available!
Jun 17 21:10:34.889 [832] dbg: dns: entering helper-app run mode
Jun 17 21:10:35.365 [832] dbg: dns: leaving helper-app run mode
Jun 17 21:10:35.424 [832] dbg: dns: entering helper-app run mode
Jun 17 21:10:40.476 [832] dbg: dns: leaving helper-app run mode
Jun 17 21:10:40.479 [832] dbg: dns: entering helper-app run mode
Jun 17 21:10:42.431 [832] dbg: dns: leaving helper-app run mode
Jun 17 21:10:42.442 [832] dbg: dns: harvest_dnsbl_queries
Return-Path: <tbtf-approval@world.std.com>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on red.laptop
X-Spam-Level:
X-Spam-Status: No, score=0.9 required=4.0 tests=BAYES_50,DCC_CHECK,
RP_MATCHES_RCVD shortcircuit=no autolearn=no autolearn_force=no
version=3.4.0
X-Spam-Relay-Country: US US US US US US
X-Spam-Language: en
Delivered-To: foo@foo.com
Received: from europe.std.com (europe.std.com [199.172.62.20])
by mail.netnoteinc.com (Postfix) with ESMTP id 392E1114061
for <foo@foo.com>; Fri, 20 Apr 2001 21:34:46 +0000 (Eire)
Received: (from daemon@localhost)
by europe.std.com (8.9.3/8.9.3) id RAA09630
for tbtf-outgoing; Fri, 20 Apr 2001 17:31:18 -0400 (EDT)
Received: from sgi04-e.std.com (sgi04-e.std.com [199.172.62.134])
by europe.std.com (8.9.3/8.9.3) with ESMTP id RAA08749
for <tbtf@facteur.std.com>; Fri, 20 Apr 2001 17:24:31 -0400 (EDT)
Received: from world.std.com (world-f.std.com [199.172.62.5])
by sgi04-e.std.com (8.9.3/8.9.3) with ESMTP id RAA8278330
for <tbtf@facteur.std.com>; Fri, 20 Apr 2001 17:24:31 -0400 (EDT)
Received: (from dawson@localhost)
by world.std.com (8.9.3/8.9.3) id RAA26781
for tbtf@world.std.com; Fri, 20 Apr 2001 17:24:31 -0400 (EDT)
Received: from sgi04-e.std.com (sgi04-e.std.com [199.172.62.134])
by europe.std.com (8.9.3/8.9.3) with ESMTP id RAA07541
for <tbtf@facteur.std.com>; Fri, 20 Apr 2001 17:12:06 -0400 (EDT)
Received: from world.std.com (world-f.std.com [199.172.62.5])
by sgi04-e.std.com (8.9.3/8.9.3) with ESMTP id RAA8416421
for <tbtf@facteur.std.com>; Fri, 20 Apr 2001 17:12:06 -0400 (EDT)
Received: from [208.192.102.193] (ppp0c199.std.com [208.192.102.199])
by world.std.com (8.9.3/8.9.3) with ESMTP id RAA14226
for <tbtf@world.std.com>; Fri, 20 Apr 2001 17:12:04 -0400 (EDT)
Mime-Version: 1.0
Message-Id: <v0421010eb70653b14e06@[208.192.102.193]>
Date: Fri, 20 Apr 2001 16:59:58 -0400
To: tbtf@world.std.com
From: Keith Dawson <dawson@world.std.com>
Subject: TBTF ping for 2001-04-20: Reviving
Content-Type: text/plain; charset="us-ascii"
Sender: tbtf-approval@world.std.com
Precedence: list
Reply-To: tbtf-approval@europe.std.com

-----BEGIN PGP SIGNED MESSAGE-----

TBTF ping for 2001-04-20: Reviving

T a s t y B i t s f r o m t h e T e c h n o l o g y F r o n
t

Timely news of the bellwethers in computer and communications
technology that will affect electronic commerce -- since 1994

Your Host: Keith Dawson

ISSN: 1524-9948

This issue: < http://tbtf.com/archive/2001-04-20.html >

To comment on this issue, please use this forum at Quick Topic:
< http://www.quicktopic.com/tbtf/H/kQGJR2TXL6H >

________________________________________________________________________

Q u o t e O f T h e M o m e n t

Even organizations that promise "privacy for their customers" rarely
if ever promise "continued privacy for their former customers..."
Once you cancel your account with any business, their promises of
keeping the information about their customers private no longer
apply... you're not a customer any longer.

This is in the large category of business behaviors that individuals
would consider immoral and deceptive -- and businesses know are not
illegal.

-- "_ankh," writing on the XNStalk mailing list

________________________________________________________________________

..TBTF's long hiatus is drawing to a close

Hail subscribers to the TBTF mailing list. Some 2,000 [1] of you
have signed up since the last issue [2] was mailed on 2000-07-20.
This brief note is the first of several I will send to this list to
excise the dead addresses prior to resuming regular publication.

While you time the contractions of the newsletter's rebirth, I in-
vite you to read the TBTF Log [3] and sign up for its separate free
subscription. Send "subscribe" (no quotes) with any subject to
tbtf-log-request@tbtf.com . I mail out collected Log items on Sun-
days.

If you need to stay more immediately on top of breaking stories,
pick up the TBTF Log's syndication file [4] or read an aggregator
that does. Examples are Slashdot's Cheesy Portal [5], Userland [6],
and Sitescooper [7]. If your news obsession runs even deeper and you
own an SMS-capable cell phone or PDA, sign up on TBTF's WebWire-
lessNow portal [8]. A free call will bring you the latest TBTF Log
headline, Jargon Scout [9] find, or Siliconium [10].

Two new columnists have bloomed on TBTF since last summer: Ted By-
field's roving_reporter [11] and Gary Stock's UnBlinking [12]. Late-
ly Byfield has been writing in unmatched depth about ICANN, but the
roving_reporter nym's roots are in commentary at the intersection of
technology and culture. Stock's UnBlinking latches onto topical sub-
jects and pursues them to the ends of the Net. These writers' voices
are compelling and utterly distinctive.

[1] http://tbtf.com/growth.html
[2] http://tbtf.com/archive/2000-07-20.html
[3] http://tbtf.com/blog/
[4] http://tbtf.com/tbtf.rdf
[5] http://www.slashdot.org/cheesyportal.shtml
[6] http://my.userland.com/
[7] http://www.sitescooper.org/
[8] http://tbtf.com/pull-wwn/
[9] http://tbtf.com/jargon-scout.html
[10] http://tbtf.com/siliconia.html
[11] http://tbtf.com/roving_reporter/
[12] http://tbtf.com/unblinking/

________________________________________________________________________

S o u r c e s

> For a complete list of TBTF's email and Web sources, see
http://tbtf.com/sources.html .

________________________________________________________________________

B e n e f a c t o r s

TBTF is free. If you get value from this publication, please visit
the TBTF Benefactors page < http://tbtf.com/the-benefactors.html >
and consider contributing to its upkeep.

________________________________________________________________________

TBTF home and archive at http://tbtf.com/ . To unsubscribe send
the message "unsubscribe" to tbtf-request@tbtf.com. TBTF is Copy-
right 1994-2000 by Keith Dawson, <dawson@world.std.com>. Commercial
use prohibited. For non-commercial purposes please forward, post,
and link as you see fit.
_______________________________________________
Keith Dawson dawson@world.std.com
Layer of ash separates morning and evening milk.

-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 6.5.2 for non-commercial use <http://www.pgp.com>

iQCVAwUBOuCi3WAMawgf2iXRAQHeAQQA3YSePSQ0XzdHZUVskFDkTfpE9XS4fHQs
WaT6a8qLZK9PdNcoz3zggM/Jnjdx6CJqNzxPEtxk9B2DoGll/C/60HWNPN+VujDu
Xav65S0P+Px4knaQcCIeCamQJ7uGcsw+CqMpNbxWYaTYmjAfkbKH1EuLC2VRwdmD
wQmwrDp70v8=
=8hLB
-----END PGP SIGNATURE-----


Spam detection software, running on the system "red.laptop",
has NOT identified this incoming email as spam. The original
message has been attached to this so you can view it or label
similar future email. If you have any questions, see
the administrator of that system for details.

Content preview: -----BEGIN PGP SIGNED MESSAGE----- TBTF ping for
2001-04-20:
Reviving T a s t y B i t s f r o m t h e T e c h n o l o g y F r o n t
[...]


Content analysis details: (0.9 points, 4.0 required)

pts rule name description
---- ----------------------
--------------------------------------------------
-1.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60%
[score: 0.5357]
1.1 DCC_CHECK Detected as bulk mail by DCC (dcc-servers.net)

$
Re: No DNS available [ In reply to ]
On 6/17/2014 4:17 PM, Walter Hurry wrote:
> Jun 17 21:10:28.016 [832] dbg: dns: servers obtained from Net::DNS :
> Jun 17 21:10:28.016 [832] dbg: dns: eval failed: available_nameservers:
> No DNS servers available!
This is the crux.

Should look something like:

Jun 17 16:27:40.311 [30240] dbg: dns: servers obtained from Net::DNS :
[127.0.0.1]:53,...

What does your /etc/resolv.conf look like?

Regards,
KAM
Re: No DNS available [ In reply to ]
On Tue, 17 Jun 2014 16:28:52 -0400, Kevin A. McGrail wrote:

> On 6/17/2014 4:17 PM, Walter Hurry wrote:
>> Jun 17 21:10:28.016 [832] dbg: dns: servers obtained from Net::DNS :
>> Jun 17 21:10:28.016 [832] dbg: dns: eval failed: available_nameservers:
>> No DNS servers available!
> This is the crux.
>
> Should look something like:
>
> Jun 17 16:27:40.311 [30240] dbg: dns: servers obtained from Net::DNS :
> [127.0.0.1]:53,...
>
> What does your /etc/resolv.conf look like?
>
$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 194.168.4.100
nameserver 194.168.8.100
$
Re: No DNS available [ In reply to ]
On 6/17/2014 5:18 PM, Walter Hurry wrote:
> On Tue, 17 Jun 2014 16:28:52 -0400, Kevin A. McGrail wrote:
>
>> On 6/17/2014 4:17 PM, Walter Hurry wrote:
>>> Jun 17 21:10:28.016 [832] dbg: dns: servers obtained from Net::DNS :
>>> Jun 17 21:10:28.016 [832] dbg: dns: eval failed: available_nameservers:
>>> No DNS servers available!
>> This is the crux.
>>
>> Should look something like:
>>
>> Jun 17 16:27:40.311 [30240] dbg: dns: servers obtained from Net::DNS :
>> [127.0.0.1]:53,...
>>
>> What does your /etc/resolv.conf look like?
>>
> $ cat /etc/resolv.conf
> # Generated by NetworkManager
> nameserver 194.168.4.100
> nameserver 194.168.8.100
You should likely be running a caching nameserver but that's a nit.

Net::DNS is unable to read your resolv.conf it appears. Are you using
selinux or anything like that?
Re: No DNS available [ In reply to ]
On Tue, 2014-06-17 at 18:03 -0400, Kevin A. McGrail wrote:
> On 6/17/2014 5:18 PM, Walter Hurry wrote:
> > On Tue, 17 Jun 2014 16:28:52 -0400, Kevin A. McGrail wrote:
> >
> >> On 6/17/2014 4:17 PM, Walter Hurry wrote:
> >>> Jun 17 21:10:28.016 [832] dbg: dns: servers obtained from Net::DNS :
> >>> Jun 17 21:10:28.016 [832] dbg: dns: eval failed: available_nameservers:
> >>> No DNS servers available!
> >> This is the crux.
> >>
> >> Should look something like:
> >>
> >> Jun 17 16:27:40.311 [30240] dbg: dns: servers obtained from Net::DNS :
> >> [127.0.0.1]:53,...
> >>
> >> What does your /etc/resolv.conf look like?
> >>
> > $ cat /etc/resolv.conf
> > # Generated by NetworkManager
> > nameserver 194.168.4.100
> > nameserver 194.168.8.100
> You should likely be running a caching nameserver but that's a nit.
>
> Net::DNS is unable to read your resolv.conf it appears. Are you using
> selinux or anything like that?
>
I'm far from certain that those are DNS servers

$ host 194.168.4.100
100.4.168.194.in-addr.arpa domain name pointer
cache1.service.virginmedia.net.
$ host 194.168.8.100
100.8.168.194.in-addr.arpa domain name pointer
cache2.service.virginmedia.net.
$

Martin
Re: No DNS available [ In reply to ]
On 6/17/2014 6:35 PM, Martin Gregorie wrote:
> On Tue, 2014-06-17 at 18:03 -0400, Kevin A. McGrail wrote:
>> On 6/17/2014 5:18 PM, Walter Hurry wrote:
>>> On Tue, 17 Jun 2014 16:28:52 -0400, Kevin A. McGrail wrote:
>>>
>>>> On 6/17/2014 4:17 PM, Walter Hurry wrote:
>>>>> Jun 17 21:10:28.016 [832] dbg: dns: servers obtained from Net::DNS :
>>>>> Jun 17 21:10:28.016 [832] dbg: dns: eval failed: available_nameservers:
>>>>> No DNS servers available!
>>>> This is the crux.
>>>>
>>>> Should look something like:
>>>>
>>>> Jun 17 16:27:40.311 [30240] dbg: dns: servers obtained from Net::DNS :
>>>> [127.0.0.1]:53,...
>>>>
>>>> What does your /etc/resolv.conf look like?
>>>>
>>> $ cat /etc/resolv.conf
>>> # Generated by NetworkManager
>>> nameserver 194.168.4.100
>>> nameserver 194.168.8.100
>> You should likely be running a caching nameserver but that's a nit.
>>
>> Net::DNS is unable to read your resolv.conf it appears. Are you using
>> selinux or anything like that?
>>
> I'm far from certain that those are DNS servers
>
> $ host 194.168.4.100
> 100.4.168.194.in-addr.arpa domain name pointer
> cache1.service.virginmedia.net.
> $ host 194.168.8.100
> 100.8.168.194.in-addr.arpa domain name pointer
> cache2.service.virginmedia.net.
> $
>
> Martin

Martin, Good call. They certainly don't work for me but some ISPs
restrict to their range. Try adding server 8.8.8.8 to use Google's
server as a test.

nslookup
> server 194.168.4.100
Default server: 194.168.4.100
Address: 194.168.4.100#53
> www.pccc.com
;; connection timed out; no servers could be reached

Then install and use a local caching nameserver. It will fix lots of
issues before they occur with a SpamAssassin installation and RBLs, etc.

Regards,
KAM
Re: No DNS available [ In reply to ]
>> Jun 17 21:10:28.016 [832] dbg: dns: servers obtained from Net::DNS :
>> Jun 17 21:10:28.016 [832] dbg: dns: eval failed:
>> available_nameservers:
>> No DNS servers available!
> This is the crux.

I can now reproduce the problem, checking ...

Mark
Re: No DNS available [ In reply to ]
> I can now reproduce the problem, checking ...
> Mark

Looks like a change in Net::DNS 0.76, which no longer has a field
$res->{nameserver}, but has now fields nameserver4 and nameserver6,
with an official access method $res->nameservers.

--- Mail/SpamAssassin/DnsResolver.pm.orig 2014-05-07
17:54:29.000000000 +0200
+++ Mail/SpamAssassin/DnsResolver.pm 2014-06-18 02:13:32.936306639
+0200
@@ -205,6 +205,8 @@
dbg("dns: servers set by config to: %s", join(', ',@ns_addr_port));
} elsif ($res) { # default as provided by Net::DNS, e.g.
/etc/resolv.conf
- @ns_addr_port = map(untaint_var("[$_]:" . $res->{port}),
- @{$res->{nameservers}});
+ my @ns = $res->UNIVERSAL::can('nameservers') ? $res->nameservers
+ :
@{$res->{nameservers}};
+ my $port = $res->UNIVERSAL::can('port') ? $res->port :
$res->{port};
+ @ns_addr_port = map(untaint_var("[$_]:" . $port), @ns);
dbg("dns: servers obtained from Net::DNS : %s", join(',
',@ns_addr_port));
}
Re: No DNS available [ In reply to ]
On 6/17/2014 8:15 PM, Mark Martinec wrote:
>> I can now reproduce the problem, checking ...
>> Mark
>
> Looks like a change in Net::DNS 0.76, which no longer has a field
> $res->{nameserver}, but has now fields nameserver4 and nameserver6,
> with an official access method $res->nameservers.
>
> --- Mail/SpamAssassin/DnsResolver.pm.orig 2014-05-07
> 17:54:29.000000000 +0200
> +++ Mail/SpamAssassin/DnsResolver.pm 2014-06-18 02:13:32.936306639
> +0200
> @@ -205,6 +205,8 @@
> dbg("dns: servers set by config to: %s", join(', ',@ns_addr_port));
> } elsif ($res) { # default as provided by Net::DNS, e.g.
> /etc/resolv.conf
> - @ns_addr_port = map(untaint_var("[$_]:" . $res->{port}),
> - @{$res->{nameservers}});
> + my @ns = $res->UNIVERSAL::can('nameservers') ? $res->nameservers
> + :
> @{$res->{nameservers}};
> + my $port = $res->UNIVERSAL::can('port') ? $res->port : $res->{port};
> + @ns_addr_port = map(untaint_var("[$_]:" . $port), @ns);
> dbg("dns: servers obtained from Net::DNS : %s", join(',
> ',@ns_addr_port));
> }

Nice catch. Can you create a bug for this so we can track it better,
please?
Re: No DNS available [ In reply to ]
On 6/17/2014 4:28 PM, Kevin A. McGrail wrote:
> On 6/17/2014 4:17 PM, Walter Hurry wrote:
>> Jun 17 21:10:28.016 [832] dbg: dns: servers obtained from Net::DNS :
>> Jun 17 21:10:28.016 [832] dbg: dns: eval failed: available_nameservers:
>> No DNS servers available!
> This is the crux.
>
> Should look something like:
>
> Jun 17 16:27:40.311 [30240] dbg: dns: servers obtained from Net::DNS :
> [127.0.0.1]:53,...
>
> What does your /etc/resolv.conf look like?

Walter, Mark Martinec found a change in Net::DNS 0.76 that likely is
your issue. He also submitted a patch which I've tested and appears to
fix your exact problem.

Can you either patch your installation based on the patch in
https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7057 or use the
svn trunk version and let us know if it works for you now?

Regards,
KAM
Re: No DNS available [ In reply to ]
On Wed, 18 Jun 2014 12:52:19 -0400, Kevin A. McGrail wrote:

> On 6/17/2014 4:28 PM, Kevin A. McGrail wrote:
>> On 6/17/2014 4:17 PM, Walter Hurry wrote:
>>> Jun 17 21:10:28.016 [832] dbg: dns: servers obtained from Net::DNS :
>>> Jun 17 21:10:28.016 [832] dbg: dns: eval failed:
>>> available_nameservers:
>>> No DNS servers available!
>> This is the crux.
>>
>> Should look something like:
>>
>> Jun 17 16:27:40.311 [30240] dbg: dns: servers obtained from Net::DNS :
>> [127.0.0.1]:53,...
>>
>> What does your /etc/resolv.conf look like?
>
> Walter, Mark Martinec found a change in Net::DNS 0.76 that likely is
> your issue. He also submitted a patch which I've tested and appears to
> fix your exact problem.
>
> Can you either patch your installation based on the patch in
> https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7057 or use the
> svn trunk version and let us know if it works for you now?

Yes, that seems to have fixed it. Many thanks to you and to Mark for your
efforts, and especially for the very quick responses.

For what it's worth, I'm actually using Net::DNS 0.77.
Re: No DNS available [ In reply to ]
On 6/18/2014 5:36 PM, Walter Hurry wrote:
> On 6/17/2014 4:28 PM, Kevin A. McGrail wrote:
>> Walter, Mark Martinec found a change in Net::DNS 0.76 that likely is
>> your issue. He also submitted a patch which I've tested and appears
>> to fix your exact problem. Can you either patch your installation
>> based on the patch in
>> https://issues.apache.org/SpamAssassin/show_bug.cgi?id=7057 or use
>> the svn trunk version and let us know if it works for you now?
> Yes, that seems to have fixed it. Many thanks to you and to Mark for your
> efforts, and especially for the very quick responses.

Thanks for the quick test. Mark did all the heavy-lifting, though.
> For what it's worth, I'm actually using Net::DNS 0.77.

It doesn't appear to be a bug. It appears to be a functionality change
that occurred with Net::DNS 0.76 so it would make sense any release
higher than that would also exhibit the behavior.

regards,
KAM