Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

I enabled the IP-in-rDNS filter, so why isn spamdyke blocking connections from servers with rDNS names that contain IP addresses?

0
Posted

I enabled the IP-in-rDNS filter, so why isn spamdyke blocking connections from servers with rDNS names that contain IP addresses?

0

The IP-in-rDNS filter requires two things to block a connection: the rDNS name must contain the IP address AND the rDNS name must contain a keyword. For example, consider the following rDNS name: 11.22.33.44.dynamic.example.com Obviously it contains an IP address (11.22.33.44), but that’s not enough to trigger the filter. If the keyword dynamic were supplied, spamdyke would block the connection. However, note that the keyword example would not be matched. This is because example is part of the last two segments of the domain name. spamdyke will not search for keywords there because that would lead to lots of false positives. It is possible to use a domain name as a keyword, if it is prefixed with a dot. For example: .example.com All connections would be blocked where the rDNS name contained the IP address and the name ended in .example.com.

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.