Spam Assassin and DNS Problems

Gimboid

• September 09, 2024 23:40

So, I have been having this issue on and off for years now and I give up googling and trying to find a permanent solution to this.

My server provider is somewhat large, so their DNS exceeds uribl.com limits and doesn't work.

My cPanel server is currently setup using PowerDNS, various online guides suggest setting up a local recursive nameserver to handle these requests, but I cannot get this to work under any circumstances.

Various guides suggest multiple different things, like setting

nameserver 127.0.0.1 

in the resolv.conf, attempting this returns as "Warning: Recursion requested but not available".

I can't believe I'm the only person with this problem, I wonder if I fudged some ancient config somewhere that is causing me this problem, but no matter what I do now, I cannot get my Spam Assassin to successfully query uribl.

Please help me :(

• 

  quietFinn

  • September 10, 2024 07:38

  If you go to WHM -> Service Configuration -> Nameserver Selection
  you see in "Disadvantages" for PowerDNS:

  • Does not provide a recursive (caching) nameserver. (requires external nameservers in resolv.conf)
    
    

   

  1
• 

  mtindor

  • October 14, 2024 12:15

  You could set up one or two simple BIND nameservers at DigitalOcean or the droplet company of your choice, and then properly configure those servers to only respond to / allow requests from your hosting server.   Sure, it does cost money.   But, at DO for instance, you can spin up an instance for $5/mo (or $10/mo with backups), configure it, and use it as a resolver.

  And then you can specifically tell SpamAssassin to use those DNS servers instead of the ones in /etc/resolv.conf by adding the following to /etc/mail/spamassassin/local.cf :

  dns_options rotate
  dns_server 1.1.1.1
  dns_server 2.2.2.2

  # where 1.1.1.1 and 2.2.2.2 are the IP addresses of the DO boxes you've set up as resolvers.

  But, seriously, you will want to / need to make sure that those servers that you set up only respond to requests made by your hosting servers.   You don't want to be setting up public resolvers.

   

  0

Please sign in to leave a comment.