My IP on DNS Blacklist suddenly stopped working. The last message says that there is an “error checking dnsbl.njabl.org” and that the host is unknown. Why does this happen and how can I get this sensor back to work again?
Article Comments
The instructions indicate that I can have a comma-separated list of blacklist services. When I try that, the sensor fails. Is this a known bug or do I just have the syntax incorrect?
Apr, 2013 - Permalink
Hi,
a comma separated list is possible but please make sure that no whitespaces are in the list, like:
server1,server2,server3
Best regards
Apr, 2013 - Permalink
Hi,
We have moved all our sensors onto the new Blacklist server and we are getting Last Message Ok Last Result 0 #
However, this is also the case when we enter www.google.com as the Blacklist server, as well as when using our own website server (which I know is not doing any sort of blacklist check).
May, 2013 - Permalink
Dear James,
I agree that this can look confusing although technically the result is correct.
The sensor works as expected: As www.google.com is not a blacklist server, the given IP is not listed, so the result is 0.
Please make sure you enter one or more valid blacklist servers in the sensor's settings.
May, 2013 - Permalink
IP on DNS Blacklist Sensor: Hotfix for “Error checking dnsbl.njabl.org” (Unknown Host)
The reason for this suddenly appearing error with the IP on DNS Blacklist Sensor is that the blacklist server dnsbl.najbl.org was shut down recently. By default, PRTG uses this server if the Blacklist Servers field is left empty. Please specify another blacklist server used for the blacklist check in the sensor settings.
Steps to Go
We recommend using bl.spamcop.net
The sensor will begin to work again immediately, using the new blacklist server.
Apr, 2013 - Permalink