> hello List, > > the name resolver works just fine on my new mailserver, but > spamassassin cannot resolve anything. spamassassin -D --lint says > > "debug: is Net::DNS::Resolver available? yes > debug: Net::DNS version: 0.48 > debug: trying (3) cingular.com... > debug: looking up NS for 'cingular.com' > debug: NS lookup of cingular.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" > > Name resolving per se works: > > [EMAIL PROTECTED]:~> nslookup intel.com -sil > Server: 192.168.0.1 > Address: 192.168.0.1#53 > > Non-authoritative answer: > Name: intel.com > Address: 198.175.96.33 > > [EMAIL PROTECTED]:~> > > Net::DNS is up to date. >
Symantec's raptor and velociraptor firewall has an internal caching nameserver that will not resolve NS records, but everything else resolves fine. Dunno if this is what you are using or not, but I had the same issue a week ago with a client that had that firewall. You can hardcode dns_available yes In your local.cf and restart to make SA skip DNS checking. However, I have found SURBL lookups are dependant on NS lookups, strange as it sounds! Without proper NS resolution, no SURBL rules will ever fire. Dallas
