blog
If you query the legacy DNSBLs via Vultr move to Spamhaus Technology’s free Data Query Service
If you are currently accessing the free legacy DNS Blocklists (DNSBLs) via the Public Mirrors, and you’re using Vultr infrastructure - you'll need to make some minor changes to your email infrastructure. The changes are easy to implement, but if you fail to do so, you could find that at some point post-May 22nd 2024, all or none of your email is blocked!
In this Blog
- The headlines for those in a hurry
- Why can’t Vultr users query the public blocklists?
- How is the free DQS different from the free Public Mirrors?
- How to access the free DQS
- How will Vultr users be prevented from querying the free DNSBLs?
- When will the error code for Vultr DNSBL users be introduced?
- What if I don’t want to use the free DQS?
- Further details
- Any questions?
Jump to
The headlines for those in a hurry
The fair use policy states that users cannot query via DNS resolvers where there is no attributable reverse DNS; this includes Vultr (we'll explain why later in this article).
To provide a clear signal to users that these blocklists are not protecting their email, Spamhaus will return an error code; 127.255.255.254. If you haven't set up your email servers to accept this error code, all emails could be rejected and bounced back to their sender.
To prevent any issues with your email stream, stop accessing the free blocklists via the Public Mirrors and start accessing the blocklists via Spamhaus Technology’s free Data Query Service (DQS), which you can sign up for here.
Once you've verified your email address, you will get access to a "DQS key" to include in your configuration. These config changes take only minutes; see the technical docs for more detail.
Why can’t Vultr users query the public blocklists?
The blocklists that are made freely available via the Public Mirrors are for small-scale, non-commercial use. To ensure these users have a good quality of service, usage is monitored and measured against the fair use policy. Vultr’s default reverse DNS masks organizations' unique identities to the Public Mirrors, so the team can’t attribute usage to individual entities. They have no way of establishing the number of queries a single organization is making. To provide transparency, these free blocklists can be accessed via Spamhaus Technology's free DQS.
How is the free DQS different from the free Public Mirrors?
Usage transparency - users register to access the free DQS and are provided with a key that records query volumes.
Increased performance - blocklists are updated in real time.
Additional protection - access to more blocklists, including: Zero Reputation Domain Blocklist, Domain Blocklist with Hostnames, and Auth Blocklist.
How to access the free DQS
Verify your email address Log in to your account and access your DQS key.
Update your email configuration. We have config guides for mainstream MTAs.
How will Vultr users be prevented from querying the free DNSBLs?
To ensure the fair use policy is adhered to, queries from IP addresses outside the policy will be blocked, and an error code will be returned. In the case of querying via an open/public resolver, i.e., Vultr, the error code is 127.255.255.254.If your MTA can't correctly parse these error codes, serious issues can occur, including bouncing all emails back to their senders and your emails not being queried against the blocklists. Here’s how to properly configure your MTA to process these error codes, if you continue to use the free Public Mirrors.
When will the error code for Vultr DNSBL users be introduced?
The error code will be slowly implemented across Vultr's IP space, commencing from Wednesday, May 22nd, 2024.Please don’t delay - take action now and move to the free DQS.
What if I don’t want to use the free DQS?
Use DNS resolvers with attributable DNS to continue being protected by Spamhaus's IP and domain reputation.
If you no longer wish for your mail stream to be protected for free by the blocklists, remove all associated configurations from your email infrastructure.
Further details
Additional information for DNSBL users having issues due to error codes is detailed here.
Previous communications that were sent in relation to these changes can be found here: Spamhaus DNSBL return codes: technical updateUsing our public mirrors? Check your return codes now
Any questions?
Not a problem – reach out to us via Twitter (@spamhaus), LinkedIn (@TheSpamhausProject) or our contact form.