Hi Benny,

It’s the authoritive nameserver giving that answer. With likely a view or acl 
response. So adding dnssec would not make much of a difference here. 

Thanks,
Raymond Dijkxhoorn

> Op 12 mei 2021 om 23:24 heeft Benny Pedersen <m...@junc.eu> het volgende 
> geschreven:
> 
> On 2021-05-12 23:01, Matthias Leisi wrote:
>>>> Am 12.05.2021 um 21:02 schrieb Michael B Allen <iop...@gmail.com>:
>>> X-Spam-Report:
>>> * -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at https://www.dnswl.org/, high
>>> *      trust
>>> *      [173.82.162.98 listed in list.dnswl.org]
>> 173.82.162.98 is not in the dnswl.org database.
>> It’s likely you’re using one of the nameservers who are not only
>> blocked from using dnswl.org free nameserver infrastructure, but where
>> we needed to use additional methods to make them stop (ab)using our
>> nameservers (namely, returning a „_HI“ result in the hope that whoever
>> is responsible will finally notice).
> 
> would it not make sense to enable dnssec on dnswl.org nameservers ?
> 
> sorry for asking, i dont know much about dns servers

Reply via email to