Perhaps I'm just using/configuring it wrong? I assumed that typing: dig www.yahoo.com At the command prompt should have SOMETHING result. Instead, I get the time out.
-Aaron -----Original Message----- From: Steven Manross [mailto:[EMAIL PROTECTED] Sent: Thursday, December 22, 2005 2:12 PM To: Aaron Boyles; SpamAssassin Subject: RE: Public Blacklists? IPs or DNS names? It wants Ips in the resolve.conf. (the version that comes with BIND is tested and works on Windows). Earlier versions crapped out on Windows with various messages. Steven -----Original Message----- From: Aaron Boyles [mailto:[EMAIL PROTECTED] Sent: Thursday, December 22, 2005 12:01 PM To: SpamAssassin Subject: RE: Public Blacklists? Hrm. I tried it, but it crapped out. :/ I used our DCs (2K3 servers) which are our DNS servers in the .conf file, but still no dice. It times out saying "no servers could be reached." Any ideas? -----Original Message----- From: Bowie Bailey [mailto:[EMAIL PROTECTED] Sent: Thursday, December 22, 2005 1:24 PM To: SpamAssassin Subject: RE: Public Blacklists? Aaron Boyles wrote: > A number of people have mentioned that... But what is it? It's not a > command my PC recognizes. > > From: SM [mailto:[EMAIL PROTECTED] > > > > nslookup is broken. :-) Use dig instead. Dig is a very nice dns lookup program that is fairly standard now on Linux. Windows still does not provide it. You can get a version for Windows here: http://pigtail.net/LRP/dig/ -- Bowie
