You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@spamassassin.apache.org by ha...@t-online.de on 2005/06/11 18:43:35 UTC
Re: DNS lookup fails
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
>>
Re: DNS lookup fails
Posted by Kenneth Porter <sh...@sewingwitch.com>.
--On Saturday, June 11, 2005 7:46 PM +0200 Stefan Ewert <nu...@gmx.net>
wrote:
> this is a single pc, so i think its better to use a nameserver from the
> www. i dont have a local nameserver running( i think ;). do i need a
> local nameserver?
Hehe, this just came up and a wiki page was created:
<http://wiki.apache.org/spamassassin/CachingNameserver>
> the problem is every time i delete this 127.0.01 and i reboot this line
> is there again.
Are you using DHCP? It will rewrite your resolv.conf unless you disable
that. It's strange that it's injecting 127.0.0.1 into resolv.conf, though,
as the typical DHCP server configuration won't provide that address.
If you can't identify what's rewriting it, try setting the immutable
attribute on resolv.conf (assuming this is ext2/3 on Linux). That prevents
even root from overwriting a file.
Re: DNS lookup fails
Posted by Stefan Ewert <nu...@gmx.net>.
Am Samstag, 11. Juni 2005 19:13 schrieb Kenneth Porter:
> --On Saturday, June 11, 2005 7:03 PM +0200 Stefan Ewert <nu...@gmx.net>
>
> wrote:
> > here ist my resolv.conf:
> >
> > nameserver 127.0.0.1
> > nameserver 217.237.151.161
> > nameserver 217.237.151.33
> >
> > after every reboot, localhost is in first place, so every querie takes
> > some time before the second nameserver is asked.
> > how do i cache values? i can run spamassassin --lint -D as often as i
> > want, nothing changes in this issue.
>
> Why are you listing anything besides 127.0.0.1? That's only useful if your
> local nameserver is down. In that case just make another resolve.conf to
> install until you fix your nameserver.
this is a single pc, so i think its better to use a nameserver from the www.
i dont have a local nameserver running( i think ;). do i need a local
nameserver?
the problem is every time i delete this 127.0.01 and i reboot this line is
there again.
Re: DNS lookup fails
Posted by Kenneth Porter <sh...@sewingwitch.com>.
--On Sunday, June 12, 2005 12:49 AM +0100 "Michele Neylon:: Blacknight"
<mi...@blacknight.ie> wrote:
> Kenneth Porter wrote:
>> Why are you listing anything besides 127.0.0.1? That's only useful if
>> your local nameserver is down. In that case just make another
>> resolve.conf to install until you fix your nameserver.
>>
> Em no. The only time 127.0.0.1 is the _only_ valid entry is if you are
> running DNS on the same machine
I think that was my point. If you're not running a local nameserver, you
shouldn't have that entry. And if you are, you don't need the others. You
wouldn't have both in to use the remote systems as a backup for the local
server, because if the local server's unstable, it shouldn't be in there at
all until you fix it.
Re: DNS lookup fails
Posted by Kenneth Porter <sh...@sewingwitch.com>.
--On Saturday, June 11, 2005 7:03 PM +0200 Stefan Ewert <nu...@gmx.net>
wrote:
> here ist my resolv.conf:
>
> nameserver 127.0.0.1
> nameserver 217.237.151.161
> nameserver 217.237.151.33
>
> after every reboot, localhost is in first place, so every querie takes
> some time before the second nameserver is asked.
> how do i cache values? i can run spamassassin --lint -D as often as i
> want, nothing changes in this issue.
Why are you listing anything besides 127.0.0.1? That's only useful if your
local nameserver is down. In that case just make another resolve.conf to
install until you fix your nameserver.
Re: DNS lookup fails
Posted by Stefan Ewert <nu...@gmx.net>.
Am Samstag, 11. Juni 2005 18:43 schrieb hamann.w@t-online.de:
> 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
>
here ist my resolv.conf:
nameserver 127.0.0.1
nameserver 217.237.151.161
nameserver 217.237.151.33
after every reboot, localhost is in first place, so every querie takes some
time before the second nameserver is asked.
how do i cache values? i can run spamassassin --lint -D as often as i want,
nothing changes in this issue.
--
"UNIX ist benutzerfreundlich - es ist nur etwas wählerisch..." (Walter Misar)