On 6/17/2014 6:35 PM, Martin Gregorie wrote:
On Tue, 2014-06-17 at 18:03 -0400, Kevin A. McGrail wrote:
On 6/17/2014 5:18 PM, Walter Hurry wrote:
On Tue, 17 Jun 2014 16:28:52 -0400, Kevin A. McGrail wrote:
On 6/17/2014 4:17 PM, Walter Hurry wrote:
Jun 17 21:10:28.016 [832] dbg: dns: servers obtained from Net::DNS :
Jun 17 21:10:28.016 [832] dbg: dns: eval failed: available_nameservers:
No DNS servers available!
This is the crux.
Should look something like:
Jun 17 16:27:40.311 [30240] dbg: dns: servers obtained from Net::DNS :
[127.0.0.1]:53,...
What does your /etc/resolv.conf look like?
$ cat /etc/resolv.conf
# Generated by NetworkManager
nameserver 194.168.4.100
nameserver 194.168.8.100
You should likely be running a caching nameserver but that's a nit.
Net::DNS is unable to read your resolv.conf it appears. Are you using
selinux or anything like that?
I'm far from certain that those are DNS servers
$ host 194.168.4.100
100.4.168.194.in-addr.arpa domain name pointer
cache1.service.virginmedia.net.
$ host 194.168.8.100
100.8.168.194.in-addr.arpa domain name pointer
cache2.service.virginmedia.net.
$
Martin
Martin, Good call. They certainly don't work for me but some ISPs
restrict to their range. Try adding server 8.8.8.8 to use Google's
server as a test.
nslookup
> server 194.168.4.100
Default server: 194.168.4.100
Address: 194.168.4.100#53
> www.pccc.com
;; connection timed out; no servers could be reached
Then install and use a local caching nameserver. It will fix lots of
issues before they occur with a SpamAssassin installation and RBLs, etc.
Regards,
KAM
