On Sat, 2 May 2020 15:59:27 +0300 Jari Fredriksson wrote: > On 2.5.2020 13.30, Reindl Harald wrote: > > and why don't you just replace /etc/resolv.conf and fire up "chattr > > +i /etc/resolv.conf" like everyone else does for years to keep it > > untouched (that's even a ducomentaed way to prevent it overwritten > > by dhcp clients) > > > > there is no point using a shared dns from whatever provider and > > it's a shame that most people are still so bound to it that they > > often fuckup even tehir own named/unbound setup with forwarders > > Thanks! I have used Linux since 1994 but was not aware of that. I'll > try it next.
You shouldn't need to do that as you can configure the DNS cache in your settings. My understanding is that masschecks are supposed to reuse network results from X-Spam-Status. Presumably the URIBL_BLOCKED warning is about lookups that occurred during the original scan rather than during the masscheck. Any network tests repeated during the masscheck would tend to corrupt the results. If you have dns_server set during scans and you are getting URIBL_BLOCKED then you have either found a bug, your DNS is diverted, or your IP address itself is blocked for some reason.
