[RFCI-Discuss] bogusmx listing of rpsa.com

[Derek J. Balling]

On Sep 4, 2006, at 11:22 PM, Abuse Desk wrote:
>>
>> rpsa.com.               43200   IN      A       0.0.0.0
>> rpsa.com.               43200   IN      NS      .
>>
>>
>>    Domain servers in listed order:
>>
>>    NS3.HOSTSVR.COM               66.180.175.156
>>    NS4.HOSTSVR.COM               72.9.101.67
>>
>> one server returns the above, another one returns nothing.
>

This is *not* a bogusmx case, it's a bogus*NS* case, one for which no  
zone exists.

- Those NS servers are reporting authoritatively *in error* as they  
are not themselves part of the NS-set that they claim to be  
authoritative ( the set ["."] ).

- Since no *valid* NS server exists, it would not be listable.

> We would agree, and renew the call for a manual-override capability  
> for
> the bogusmx zone.

Bogusmx is based entirely on "technical" standards. If you can't  
automate a test for it, then it has no place in the zone. In this  
case, while it's fairly clear that the individuals are "broken", they  
are not broken in a manner consistent with inclusion in the bogusmx  
zone.

Cheers,
D




-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 2419 bytes
Desc: not available
Url : http://lists.megacity.org/pipermail/rfci-discuss/attachments/20060905/2e8e67fb/smime.bin