On 3/8/13 2:04 AM, Steven Carr wrote:
> I'm having the same issues with zone transfers timing out, but I can
> perform queries directly to the RPZ servers, so there is nothing wrong
> from the network/firewall side of things.
>
> sjcarr@elmo:~ $ dig +vc 1.68.10.103.in-addr.arpa.drop.rpz.spamhaus.
hi,
with all of your questions/guidance, I made some progress.
definitely some PEBKAC. made mapping adjustment/correction in my NAT
src mapping table.
checking
dig soa rpz.spamhaus.org @199.168.90.52
; <<>> DiG 9.9.2-rpz+rl.028.23-P1 <<>> soa
rpz.spamha
On 8 March 2013 00:49, Vernon Schryver wrote:
> The RPZ log captures only information about response policy zone
> rewriting. A response policy zone is the same as every other local
> zone, so most problems with the zone itself are logged elsewhere.
>
> Depending on your ACLs, you can probe a res
> From: pgbi...@ml1.net
> i've registered my nameserver IP with spamhaus for use of its RPZ list;
> i've been approved for access.
> 07-Mar-2013 13:26:25.657 xfer-in: error: transfer of
> 'drop.rpz.spamhaus.org/IN/internal' from 199.168.90.51#53:
> failed to connect: timed out
Verify that you can query their name server like so:
dig soa rpz.spamhaus.org @199.168.90.52
and if that is successful, test that you can perform a transfer:
dig axfr rpz.spamhaus.org @199.168.90.52
I can tell you that my slaves to Spamhaus's name servers are working just
fine.
On Thu, Mar
hi,
i've installed
named -v
BIND 9.9.2-rpz+rl.028.23-P1
i've registered my nameserver IP with spamhaus for use of its RPZ list;
i've been approved for access.
i've setup my bind9 conf for slave access to a spamhaus RPZ
...
acl rpz4_spamhaus { 199.168.90.51; 199.168.90.52
6 matches
Mail list logo
