You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I do not know if this goes against the design rules,
but it would be very useful to block clients from the dashboard,
it would be very useful in vps, as there are many companies scanning dns servers,
and it is annoying to see unknown clients.
in my case, sometimes there are up to 15 unknown ip addresses in 24 hours,
and it is boring to add one by one to the blacklist in the dns settings,
a button would do it faster, and would have better control.
it could be something similar to blocking address in query log.
like this:
The text was updated successfully, but these errors were encountered:
JoseGalRe
changed the title
[Feature Request] add button to block client in top clients from dashboard?
[Feature Request] Add button to block client in top clients from dashboard?
Jul 20, 2019
Additionally, we should highlight clients that are blocked (i.e. access is denied for this IP address). All the work should be done on the client-side.
If the client is blocked, there should be the "Unblock" button.
There should be a confirmation dialog shown when user clicks "Block" or "Unblock".
In the beta version using this button, sometimes leads to losing everything I had in the DNS settings including the "Disallowed clients" list and the blocked domains list.
@IldarKamalov you should request the current DNS settings before modifying it.
Also, don't refresh the full page every time you block or unblock a client.
I do not know if this goes against the design rules,
but it would be very useful to block clients from the dashboard,
it would be very useful in vps, as there are many companies scanning dns servers,
and it is annoying to see unknown clients.
in my case, sometimes there are up to 15 unknown ip addresses in 24 hours,
and it is boring to add one by one to the blacklist in the dns settings,
a button would do it faster, and would have better control.
it could be something similar to blocking address in query log.
like this:
The text was updated successfully, but these errors were encountered: