Hi,
I noticed exactly the same yesterday, and when I tried again it worked.
So I would assume that Net::DNS uses some timeouts which are rather short, to
retrieve
data from my local dns cache Second time through, it will get cached values
sooooooperfast and be happy
Wolfgang Hamann .
>> Hi,
>> im running spamassassin --lint -D and get the following error:
>> debug: is Net::DNS::Resolver available? yes
>> debug: Net::DNS version: 0.51
>> debug: trying (3) motorola.com...
>> debug: looking up NS for 'motorola.com'
>> debug: NS lookup of motorola.com failed horribly =3D> Perhaps your resolv.c=
>> onf=20
>> isn't pointing at a valid server?
>> debug: All NS queries failed =3D> DNS unavailable (set dns_available to=20
>> override)
>> debug: is DNS available? 0
>>
>> I got SA version 3.0.3 and the nameserver in resolv.conf are ok.
>> can u tell me where to search for the problem.=20
>> NET::DNS works also, i tried this with a small perl script:
>> #!/usr/bin/perl -w
>> =20
>> use Net::DNS;
>> =20
>> $domain =3D $ARGV[0] || die "usage: $0 domain";
>> =20
>> $resolver =3D new Net::DNS::Resolver;
>> =20
>> # MX-Record abfragen=20
>> @mx =3D mx($resolver, $domain);
>> =20
>> if (@mx) {
>> # Erfolg! =DCber alle Resource Records iterieren
>> foreach $rr (@mx) {
>> print $rr->preference, " ",=20
>> $rr->exchange, "\n";
>> }
>> } else {
>> # Leere Liste, Fehler!
>> print "Kein MX-Record f=FCr $domain: ",=20
>> $resolver->errorstring, "\n";
>> }
>>
>> thanks for help
>> stefan
>> =2D-=20
>> The remaining work to finish in order to reach your goal increases as=20
>> the deadline approaches
>> -- Murphy's Laws of Computation n=B01
>>
