You mentioned firewall. Is it possible that you are not opening up the right connections to localhost or to the 192.x.x.x machine?
We tend to mix firewall and server software on the same machine from many small small clients. I'm assuming that you are using iptables. Did you open up lo for all traffic to and from itself? Port 53 tcp and udp to/through the firewall? You can test if the resolv.conf is pointing to the proper location after the change. Just run a nslookup and see which server it wants to pickup -----Original Message----- From: Chris [mailto:[EMAIL PROTECTED] Sent: Saturday, September 10, 2005 9:43 AM To: users@spamassassin.apache.org Subject: Re: Net::DNS install assistance > > Should there be a different ip, ie..127.0.0.1 instead of 192.168.1.2? > > Likely. That is what I have. I run the name server on the same machine > as SpamAssassin so it's 127.0.0.1 rather than the external address. > (And yes, I do know I am a bad girl for mixing firewall and servers on > the same machine.) > > {^_^} Thats what I thought. I changed my resolv.conf to show nameserver 127.0.0.1 did a network restart, but the Net::DNS tests are determined to use 192.168.1.2, I wonder if a system restart is needed? -- Chris Registered Linux User 283774 http://counter.li.org 11:41:04 up 17:02, 1 user, load average: 1.04, 1.18, 1.04 Mandriva Linux 10.1 Official, kernel 2.6.8.1-12mdk
