Yes, this has never worked for me either. This is just a cPanel bug that has never been tested or verified by cPanel's staff. Let me provide a little more details:
I'm not sure if you would say it's a problem with "Frontpage (re)install" or with the "IP Deny Manager", but the problem is caused by a broken .htaccess configuration installed from FP Extensions. To fix the buggy .htaccess configuration, simply UNinstall Frontpage extensions and the bugs get deleted with it. (Never ever install frontpage extensions again or the bug will come back). Then whatever IPs you add using cPanel's "IP Deny Manager" will be banned perfectly. (You just need to add them again since uninstalling frontpage takes everything with it into the bit-bucket.)
If you want frontpage installed AND want to use IP Deny Manager, then you can add a cron using the "Stanard Cron Job Manager" to undo the cPanel bugs as follows:
* * * * * perl -p -i -e 's/deny,allow/allow,deny/' ~/public_html/.htaccess
Or set it to run every hour or every day or whatever. Or you can just run this perl line from command prompt after every time you install frontpage extensions. Running this command will perform the following repairs:
I'm surprised that Jemshi didn't just say that this is a bug instead of pretending like everything was working. I guess Jemshi just didn't have FrontPage enabled when testing.
Hopefully, someone is strong enough to convince Nick to repair the "IP Deny Manager" to start fixing the order command on-the-fly to ensure that "deny" is LAST in order to force the deny settings to override any allow settings.
cPanel.net Support Ticket Number: