Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
it is probably safe to say that the above can be true - for a peculiar reason though.
Nginx, as shipped with Plesk, should not contain the ngx_http_limit_req_module - you can verify this with the command : nginx -V
However, as far as I know, you can simply declare the limit_req_zone directive, without resulting in errors at config check (via the command : nginx -t ).
I do not (yet) know whether it can be recommended to use the limit_req_zone directive, I still have to find time to get some decent checks designed and executed.
It could work though, so that is the good news - but you can imagine by now that the output of Nginx -V obfuscates the potential usage of the limit_req_zone directive.
Anyway, you should note that - in general - it is a better idea to keep bad traffic from entering the proxy level (Nginx) or the webserver level (Apache) : also use a firewall!
......... and so are a lot of other modules, which are not compiled into the Nginx version shipped with Plesk.
Not to mention the fact that Nginx core is actually intended for commercial subscriptions, with the community variant being some form of testing playground.
In essence, the whole concept of Nginx is a bit different from what one might expect - I will not bother you with the details.