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
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
I am running the latest version
I checked the documentation and found no answer
I checked to make sure that this issue has not already been filed
Problem Description
When going to the Query Log (which I often do), I often see the Block button right next to the client IP, and I often have to remember that the button instead blocks the domain name much further to the left.
This has inspired me to think: Why not add a Block Client button there as well, which automatically adds the client IP to DNS Settings → Disallowed Clients?
As seen in the screenshot below, it would have saved me a bit of time to simply block highly questionable clients like these directly from the logger, instead of marking and copying the IPs and manually pasting them into Disallowed Clients.
Proposed Solution
Described in Problem Description above.
Alternatives Considered
None that are realistic. Especially if we exclude dramatic things like adding an option to disallow all PR-Chinese IPs by default, which probably isn't even relevant to this feature request.
Additional Information
May or may not cause conflicts (or simply require some extra adaption work) with #1032, should that one ever become implemented.
The text was updated successfully, but these errors were encountered:
I have also received a large number of DNS requests for " pizzaseo.com" recently. Is there any better way to solve this problem once and for all, except for the ban on clients?
Prerequisites
Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.
Problem Description
When going to the Query Log (which I often do), I often see the
Block
button right next to the client IP, and I often have to remember that the button instead blocks the domain name much further to the left.This has inspired me to think: Why not add a
Block Client
button there as well, which automatically adds the client IP to DNS Settings → Disallowed Clients?As seen in the screenshot below, it would have saved me a bit of time to simply block highly questionable clients like these directly from the logger, instead of marking and copying the IPs and manually pasting them into Disallowed Clients.
Proposed Solution
Described in Problem Description above.
Alternatives Considered
None that are realistic. Especially if we exclude dramatic things like adding an option to disallow all PR-Chinese IPs by default, which probably isn't even relevant to this feature request.
Additional Information
May or may not cause conflicts (or simply require some extra adaption work) with #1032, should that one ever become implemented.
The text was updated successfully, but these errors were encountered: