Gary V > Was there absolutely no output? If there was it may help to see it. > There have been cases of a corrupt perl module Net::DNS exhibiting > somewhat similar behavior. it is up to date > See if your copy is up to date. Also make sure your resolver works: it works properly:
Russ Ochsner > ... > Make sure you have those ip addresses in your DNS reverse lookup > zone. It may just be taking a long time because your resolver times out on > each against the authoritative dns server for your ip block. I did it, but I got nothing. But for your suggestions: you have put me on the right way: the 2 servers (one cluster) have to replace our existing server. I tried to unplug :O) the cable that connected the cluster to our switch. Amavis started to work properly. It seems that amavis have been tricked by our "official" DNS server. Don't know how exactily this could be: /etc/resolv.conf contains only 127.0.0.1 as DNS, so each server of the cluster should query itself. Obviously each machine has its own istance of bind running. The strange thing is that if I did ping or nslookup I got the right IP. Again, thanks for your interest and the suggestions ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
