[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: question about return code .255


Hello Patrick,

Thanks for the reply.

I really should have said local-unbound - the FreeBSD built-in version.

I also see the same return on a friend's postfix server to about 50% of 
queries.  No problem with zen on his server either.

I get your point about not being very useful in postscreen.  

Cheers,
Phil

Sunday, January 26, 2025, 4:27:07 PM, you wrote:

> I am also using unbound.
> I went through my logs for the last 6 months, and I have never seen  
> this response code.

> I found dnswl didn't help postscreen at all, and removed it from my  
> postscreen config.

> It does look like I don't do a lot of lookups to dnswl though, since  
> most ip's have already made it onto my whitelist or blacklist due to  
> previous reputation and do not need to be queried.

> Quoting Phil <mb240920@xxxxxx>:

>> Hi,
>>
>> I just subscribed to this list, so hoping this finds its way into  
>> the existing thread.
>>
>> I also see the return code 127.0.0.255 sometimes while using
>> postfix/postscreen with a caching resolver (unbound) on FreeSBD 14.2.
>>
>> My unbound config works fine for everything else, including queries to
>> zen.spamhaus.org.  It's unlikely that spamhaus would accept those if I was
>> using a public DNS.
>>
>> --
>> Best regards,
>> Phil







-- 
Best regards,
Phil


References:
Re: question about return code .255Phil <mb240920@xxxxxx>
Re: question about return code .255Patrick Domack <patrickdk@xxxxxxxxxxxxx>