Skip to main content

Query to URIBL was blocked - How do I set up a caching nameserver?

Comments

10 comments

  • keat63
    I went through this 2 years ago, can I remember what I did ? No. Can i remember if I even rolled back. No. Did I find my original post. Yes DNS implications to modifying resolv.conf hope this helps
    0
  • DigitalEssence
    Thanks for the link to your post. It looks as though I need to add a dns_server directive to my /etc/mail/spamassassin/local.cf file rather than mucking around with resolv.conf. I see that URIBL.COM - Realtime URI Blacklist provide public DNS feeds for low volume users and have a nice map but don't know whetehr I just need to ping say ff.uribl.com to find it's IP address to enter into the dns_server config. UPDATE: I use MailScanner for my spam scanning and while this does use SpamAssassin, it seems that this fix won't work. I will continue digging.
    0
  • cPanelMichael
    Hello, Have you considered using different resolvers in your /etc/resolv.conf file? For instance, does your data center offer their own resolvers for you to use instead of the Google public resolvers? Thank you.
    0
  • DigitalEssence
    Thanks for everyone's help, I'm all sorted! The issue was that the host added my server IP address in resolv.conf where it should have been the Loopback address. Once I'd added this to the top of the list, Exim started to block emails based on RBL checks and then a quick restart of MailScanner and I'm seeing RBL checks in the logs and no blocked messages. I've kept in the original Google servers as a fallback (I assume that's how it works) and for anyone else with this issue, here is a copy of my resolv.conf > cat resolv.conf # Generated by SolusVM nameserver 127.0.0.1 nameserver 8.8.8.8 nameserver 8.8.4.4 Thanks, Heds
    0
  • cPanelMichael
    I'm happy to see the issue is now resolved. Thank you for updating us with the outcome.
    0
  • aztopdavid
    DNS implications to modifying resolv.conf hope this helps

    Yes, it just helped me. My SpamAssassin queries to URIBL and DNSWL have been blocked for well over a year, and it was finally resolved by adding dns_server 127.0.0.0 to /etc/mail/spamassassin/local.cf (see the "DNS implications..." link for more details).
    0
  • Shoss
    Yes, it just helped me. My SpamAssassin queries to URIBL and DNSWL have been blocked for well over a year, and it was finally resolved by adding dns_server 127.0.0.0 to /etc/mail/spamassassin/local.cf (see the "DNS implications..." link for more details).

    Hi! could you share your /etc/mail/spamassassin/local.cf and /etc/resolv.conf files?
    0
  • aztopdavid
    I'll give you just the relevant bits: In my /etc/mail/spamassassin/l local.cf file, I added this at the end: dns_server 127.0.0.1 # added to fix blocking of URIBL and DNSWL queries My resolv.conf file has two "nameserver" entries with the ip addresses of two of my host's resolvers
    0
  • Shoss
    I'll give you just the relevant bits: In my /etc/mail/spamassassin/l local.cf file, I added this at the end: dns_server 127.0.0.1 # added to fix blocking of URIBL and DNSWL queries My resolv.conf file has two "nameserver" entries with the ip addresses of two of my host's resolvers

    Thanks a lot for clarifying this. Apart from a cPanel server, I have a DA server where I put the following: cat /etc/resolv.conf nameserver 127.0.0.1 nameserver 74.x.x.x nameserver 74.x.x.x After adding the loopback address, the issue appears to have been solved, but effectively made the server a recursive DNS resolver. I will try the local.cnf method on the cPanel server now.
    0
  • renecd
    Suggestions here assume using Bind. Powerdns, which appears to be the recommended solution, does not provide a caching nameserver. How to fix? Ordinarily I'd just install a Powerdns Recursor, but I'm always a bit worried about how that will affect WHM's own Powerdns Auth server.
    0

Please sign in to leave a comment.