[prev in list] [next in list] [prev in thread] [next in thread] 

List:       inet-access
Subject:    Re: Problems with Spamcop -- Resolving bl.spamcop.net?
From:       John Payne <john () sackheads ! org>
Date:       2004-07-15 17:21:03
Message-ID: 598C4AF8-D683-11D8-AF19-000A95AF3094 () sackheads ! org
[Download RAW message or body]


On Jul 15, 2004, at 11:17 AM, Paul Chvostek wrote:

> On Wed, Jul 14, 2004 at 03:19:54PM -0400, John Payne wrote:
>>
>> On Jul 14, 2004, at 3:17 PM, Steve Glines wrote:
>>
>>> $ host bl.spamcop.net
>>> Host bl.spamcop.net not found: 2(SERVFAIL)
>>
>> I'm not surprised to find out that there is no A record for
>> bl.spamcop.net
>
> SERVFAIL != NXDOMAIN

Yes, but testing something that's unknown to exist and getting an error 
message doesn't mean anything.

$ host 2.0.0.127.bl.spamcop.net
2.0.0.127.bl.spamcop.net has address 127.0.0.2

bl.spamcop.net is delegated to a whole set of blns nameservers.  It 
wouldn't surprise me to find that their implementation details have 
ignored the possibility of querying bl.spamcop.net as opposed to 
ip.ad.dr.ess.bl.spamcop.net:

$ dig bl.spamcop.net any @blns8.spamcop.net

; <<>> DiG 9.2.2 <<>> bl.spamcop.net any @blns8.spamcop.net
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 60074
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

is host translating REFUSED to SERVFAIL perhaps?

_______________________________________________
"Eat sushi frequently". - Avi
inet@inet-access.net is the human contact address.
list@inet-access.net is the list posting address.
See below URL for subscribe/unsubscribe and list options:
http://inet-access.net/mailman/listinfo/list
[prev in list] [next in list] [prev in thread] [next in thread]