At 09:07 2010-01-29 -0200, Wagner Pereira wrote:
Well, maybe because there is a problem in my DNS configuration.
When I ran the nslookup command here in my station, this happened:
C:\...> nslookup rtracker.rt.pop-sp.rnp.br
Servidor: kliper.pop-sp.rnp.br
Address: 200.133.192.62
$ host rtracker.rt.pop-sp.rnp.br
Host rtracker.rt.pop-sp.rnp.br not found: 3(NXDOMAIN)
It appears that the DNS is probably being resolved by a private nameserver
(say, on your LAN, or otherwise firewalled). It is quote possible you have
a host that believes it is authoritative, but won't answer queries to the
outside world.
$ host -t NS rnp.br
rnp.br name server lua.na-df.rnp.br.
rnp.br name server bellana.nc-rj.rnp.br.
rnp.br name server teyr.na-cp.rnp.br.
$ host -t NS pop-sp.rnp.br
pop-sp.rnp.br name server dnssecond.pop-sp.rnp.br.
pop-sp.rnp.br name server parom.pop-sp.rnp.br.
pop-sp.rnp.br name server bellana.nc-rj.rnp.br.
pop-sp.rnp.br name server kliper.pop-sp.rnp.br.
This is system config stuff, not procmail (in fact, PROCMAIL itself doesn't
perform any DNS queries).
[snip - trimmage is good practice]
---
Sean B. Straw / Professional Software Engineering
Procmail disclaimer: <http://www.professional.org/procmail/disclaimer.html>
Please DO NOT carbon me on list replies. I'll get my copy from the list.
____________________________________________________________
procmail mailing list Procmail homepage: http://www.procmail.org/
procmail(_at_)lists(_dot_)RWTH-Aachen(_dot_)de
http://mailman.rwth-aachen.de/mailman/listinfo/procmail