Taking a stab at you meaning "block all IPs that reverse resolve to a name
managed by secureserver.net" because their servers keep scanning you.
You could craft a fail2ban recipe to reverse resolve the IP address (after
a some threshold of rejected packets) then block that IP if it '
secureserver.
On 10/6/2015 6:34 AM, Leon Fauster wrote:
--On Monday, October 05, 2015 10:46 AM -0400 "James B.
Byrne" wrote:
>So, is there any convenient way to construct an IPTables rule to block
>all IPs associated with a given Domain Name server?
IPs have the reversed lookup "assosiated" with a NS.
Wh
--On Monday, October 05, 2015 10:46 AM -0400 "James B. Byrne"
wrote:
> So, is there any convenient way to construct an IPTables rule to block
> all IPs associated with a given Domain Name server?
IPs have the reversed lookup "assosiated" with a NS.
What do you mean with "associated"?
Do mea
On 6 October 2015 at 00:46, James B. Byrne wrote:
> So, is there any convenient way to construct an IPTables rule to block
> all IPs associated with a given Domain Name server?
>
You can use ipsets to block a large collection of IP addresses with
netfilter. I block various problematic countrie
--On Monday, October 05, 2015 10:46 AM -0400 "James B. Byrne"
wrote:
So, is there any convenient way to construct an IPTables rule to block
all IPs associated with a given Domain Name server?
Doing DNS queries within the kernel netfilter path would be bad.
You could run a cron job to update
This is the same origin that I reported on earlier. Apparently asking
for an explanation of why they were probing our sites only encouraged
them to make additional attempts.
sshd:
Authentication Failures:
unknown (ip-173-201-178-18.ip.secureserver.net): 2 Time(s)
unknown (ip-97
6 matches
Mail list logo
