Re: DNS lookup fails
--On Sunday, June 12, 2005 12:49 AM +0100 Michele Neylon:: Blacknight [EMAIL PROTECTED] 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
Am Sonntag, 12. Juni 2005 01:39 schrieb Thomas Cameron: On Sat, 2005-06-11 at 18:41 +0200, Stefan Ewert wrote: but as you can see im using dns version 0.51 and it doesnt work for me. so if anyone has another suggest id happy to hear about it ;) 0.51 didn't work for me, either on RHEL 2.1. I had to downgrade to http://www.net-dns.org/download/Net-DNS-0.48_01.tar.gz. 0.48_3 was b0rken for me, too. ok i downgraded to 0.48_1 and now it works for me too. should i file a bugreport or did anyone of you already do this? -- Microsoft's biggest and most dangerous contribution to the software industry may be the degree to which it has lowered user expectations.
Re: DNS lookup fails
Quoting Stefan Ewert [EMAIL PROTECTED]: Am Sonntag, 12. Juni 2005 01:39 schrieb Thomas Cameron: On Sat, 2005-06-11 at 18:41 +0200, Stefan Ewert wrote: but as you can see im using dns version 0.51 and it doesnt work for me. so if anyone has another suggest id happy to hear about it ;) 0.51 didn't work for me, either on RHEL 2.1. I had to downgrade to http://www.net-dns.org/download/Net-DNS-0.48_01.tar.gz. 0.48_3 was b0rken for me, too. ok i downgraded to 0.48_1 and now it works for me too. should i file a bugreport or did anyone of you already do this? I got lt errors with 0.48_01 and so on. 0.49 works fine. 0.50 0.51 gives me mx.al deprecated/missing errors. Regards, d.
Re: [solved] DNS lookup fails
Am Sonntag, 12. Juni 2005 09:09 schrieb Stefan Ewert: Am Sonntag, 12. Juni 2005 01:39 schrieb Thomas Cameron: On Sat, 2005-06-11 at 18:41 +0200, Stefan Ewert wrote: but as you can see im using dns version 0.51 and it doesnt work for me. so if anyone has another suggest id happy to hear about it ;) 0.51 didn't work for me, either on RHEL 2.1. I had to downgrade to http://www.net-dns.org/download/Net-DNS-0.48_01.tar.gz. 0.48_3 was b0rken for me, too. ok i downgraded to 0.48_1 and now it works for me too. should i file a bugreport or did anyone of you already do this? hi, one add from me: i upgraded to Net::DNS 0.49 (the last one thats working AFAIK) and changed in my /etc/nsswitch.conf the following: hosts: files dns to hosts: dns files now the first nameserver in resolv.conf isnt localhost anymore and dhcp is working fine too! have a nice week
DNS lookup fails
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 = Perhaps your resolv.conf
isn't pointing at a valid server?
debug: All NS queries failed = DNS unavailable (set dns_available to
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.
NET::DNS works also, i tried this with a small perl script:
#!/usr/bin/perl -w
use Net::DNS;
$domain = $ARGV[0] || die usage: $0 domain;
$resolver = new Net::DNS::Resolver;
# MX-Record abfragen
@mx = mx($resolver, $domain);
if (@mx) {
# Erfolg! Über alle Resource Records iterieren
foreach $rr (@mx) {
print $rr-preference, ,
$rr-exchange, \n;
}
} else {
# Leere Liste, Fehler!
print Kein MX-Record für $domain: ,
$resolver-errorstring, \n;
}
thanks for help
stefan
--
The remaining work to finish in order to reach your goal increases as
the deadline approaches
-- Murphy's Laws of Computation n°1
Re: DNS lookup fails
Stefan Ewert wrote:
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 = Perhaps your resolv.conf
isn't pointing at a valid server?
debug: All NS queries failed = DNS unavailable (set dns_available to
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.
NET::DNS works also, i tried this with a small perl script:
#!/usr/bin/perl -w
use Net::DNS;
$domain = $ARGV[0] || die usage: $0 domain;
$resolver = new Net::DNS::Resolver;
# MX-Record abfragen
@mx = mx($resolver, $domain);
if (@mx) {
# Erfolg! Über alle Resource Records iterieren
foreach $rr (@mx) {
print $rr-preference, ,
$rr-exchange, \n;
}
} else {
# Leere Liste, Fehler!
print Kein MX-Record für $domain: ,
$resolver-errorstring, \n;
}
thanks for help
stefan
Hi,
As was mentioned yesterday on the list, Net::DNS 0.50 seems to be
broken. If you are running 0.50, upgrade to 0.51 or downgrade to 0.48
Regards,
Rick
Re: DNS lookup fails
Am Samstag, 11. Juni 2005 18:03 schrieb Stefan Ewert:
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 = Perhaps your
resolv.conf isn't pointing at a valid server?
debug: All NS queries failed = DNS unavailable (set dns_available to
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.
NET::DNS works also, i tried this with a small perl script:
#!/usr/bin/perl -w
use Net::DNS;
$domain = $ARGV[0] || die usage: $0 domain;
$resolver = new Net::DNS::Resolver;
# MX-Record abfragen
@mx = mx($resolver, $domain);
if (@mx) {
# Erfolg! Über alle Resource Records iterieren
foreach $rr (@mx) {
print $rr-preference, ,
$rr-exchange, \n;
}
} else {
# Leere Liste, Fehler!
print Kein MX-Record für $domain: ,
$resolver-errorstring, \n;
}
i got the following answer (pm):
Hi,
As was mentioned yesterday on the list, Net::DNS 0.50 seems to be
broken. If you are running 0.50, upgrade to 0.51 or downgrade to 0.48
end of mail
but as you can see im using dns version 0.51 and it doesnt work for me. so if
anyone has another suggest id happy to hear about it ;)
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
sooperfast 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
Am Samstag, 11. Juni 2005 18:43 schrieb [EMAIL PROTECTED]: 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 sooperfast 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)
Re: DNS lookup fails
--On Saturday, June 11, 2005 7:03 PM +0200 Stefan Ewert [EMAIL PROTECTED] 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
Am Samstag, 11. Juni 2005 19:13 schrieb Kenneth Porter: --On Saturday, June 11, 2005 7:03 PM +0200 Stefan Ewert [EMAIL PROTECTED] 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
--On Saturday, June 11, 2005 7:46 PM +0200 Stefan Ewert [EMAIL PROTECTED] 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
On Sat, 2005-06-11 at 12:15 -0400, Rick Macdougall wrote: Hi, As was mentioned yesterday on the list, Net::DNS 0.50 seems to be broken. If you are running 0.50, upgrade to 0.51 or downgrade to 0.48 I found that I had to downgrade to 0.48_1, 0.48_3 was broken. YMMV. Thomas
Re: DNS lookup fails
On Sat, 2005-06-11 at 18:41 +0200, Stefan Ewert wrote: but as you can see im using dns version 0.51 and it doesnt work for me. so if anyone has another suggest id happy to hear about it ;) 0.51 didn't work for me, either on RHEL 2.1. I had to downgrade to http://www.net-dns.org/download/Net-DNS-0.48_01.tar.gz. 0.48_3 was b0rken for me, too. Thomas
