On Thu, May 09, 2002 at 11:03:22PM +0200, Nipper, Arnold wrote:
> dig just times out if no nameserver is given in resolv.conf ....
Not surprising. No nameserver means no configuration, so what is dig
supposed to do?
But you had a nameserver line in there, and could check for MX using
dig, correct? If not, add "nameserver 127.0.0.1" and try again. If so,
continue.
Run this command. If it fails, and you can do "dig yahoo.com mx",
then there is definately a problem with Net::DNS.
perl -e 'require Net::DNS; $t=Net::DNS::Resolver->new;' \
-e 'if ( defined $t ) { @mx = Net::DNS::mx($t,"yahoo.com") }' \
-e 'else { die "Can not get Net::DNS working!\n" }' \
-e 'print $#mx+1," mx entries found!\n"'
What to do at that point ...? Good question. What version of Net::DNS
are you using? I know that 0.12 seems to have no issues and is the
latest stable version. If you're also using 0.12 then non-SA related
debugging will have to take place.
Might you have a firewall rule that could be blocking the traffic
to/from localhost? There may be a difference between how dig, host,
and Net::DNS do queries against the server which could be blocked.
--
Randomly Generated Tagline:
He may have come up with the recipe, but I came up with the idea of
charging $6.95 for it.
-- Moe Syzlak
Flaming Moe's
_______________________________________________________________
Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: [EMAIL PROTECTED]
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
