...
Just as in the regular lookup case DNSBLv5APIv3: getListed (POST).
...
Variants
Be careful with the variant described here. Putting data into the system do support multiple addresses. This however, changes the requirements of the input data object. In the old API, adding data without a bitmasked value would set the bitmask value 64 to the host (IP_ABUSE_NO_SMTP). In the APIv3 service empty bitmasks on multiple hosts are not allowed, since we prefer to get proper values on each added host (in case they are different to each other). So, this does not work:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
{
"response": [],
"errors": {
"code": "400",
"success": "",
"faultstring": "Updating or adding multiple entries requires a syntax with associative arrays (arrays with keys)"
}
} |
...
Request of adding/updating multiple hosts
To be more specific with what kind of address you're adding, you can also format your input syntax like this:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
{
"dnsblResponse": {
"status": [{
"address": "44.11.12.77",
"arpa": "77.12.11.44",
"state": "new",
"arpaDelegations": [
"77.12.11.44.dnsbl.tornevall.org"
],
"flag": "32"
},
{
"address": "18.33.14.30",
"arpa": "30.14.33.18",
"state": "new",
"arpaDelegations": [
"30.14.33.18.dnsbl.tornevall.org",
"30.14.33.18.bl.fraudbl.org"
],
"flag": "102"
}
]
}
} |
States
States in the response output can be new and update (if the state is "new" - the host has been added - and "updated" for hosts that already exists in the database).
The update-state might affect the hit ratio of the blacklist. This means that if someone recently requested for removal in the system and the host are again discovered by the DNSBL, a penalty timer can be added to the restored host. In this way, hosts that is popular spam targets, renders a high risk making it harder to get delisted in the future. Unless the administrators gets the problems solved.