Barry Margolin wrote:
> > 3. Incorrect behaviour by the resolver behind 95.102.17.107.
>
> Could it be the built-in resolver in spamming software?
That's plausible, especially in relation to MX records.
--
Ronan Flood
___
bind-users mailing list
bi
In article ,
Ronan Flood wrote:
> Barry Margolin wrote:
>
> > This suggests one of the following problems:
> >
> > 1. 95.102.17.107 is pointing to your nameserver in its resolver
> > configuration, but your server doesn't allow them to use you as a
> > resolver (the IP isn't in your allow-r
Barry Margolin wrote:
> This suggests one of the following problems:
>
> 1. 95.102.17.107 is pointing to your nameserver in its resolver
> configuration, but your server doesn't allow them to use you as a
> resolver (the IP isn't in your allow-recursion and allow-query-cache
> ACL).
>
> 2. T
ue to any problem.
-Original Message-
From: bind-users-boun...@lists.isc.org
[mailto:bind-users-boun...@lists.isc.org] On Behalf Of Barry Margolin
Sent: Friday, March 20, 2009 1:07 PM
To: comp-protocols-dns-b...@isc.org
Subject: Re: query (cache) 'coriander.plus.com/A/IN' den
log message
>
> 20-Mar-2009 16:32:54.984 security: info: client 95.102.17.107#14080: query =
> (cache) 'coriander.plus.com/A/IN' denied
Is it always the same client IP? That IP is some random DSL user in
Slovakia.
>
> And in the clients zone fi
7.107#14080: query
(cache) 'coriander.plus.com/A/IN' denied
And in the clients zone file we have
@ IN MX 10 coriander.plus.com.
Is this anything to worry about? How can I determine if the client is receiving
email - without asking - because these appear
6 matches
Mail list logo
