Thanks for your help. I had some trouble with the log file and after I
got it going I identified the point of failure quickly. The firewall was
misconfigured and applied NAT on internal traffic. However, someone
mentioned that idea. Otherwise I'd probably had banged my head for hours
seeing the
On 26 April 2017 at 08:23, Nico CARTRON wrote:
> BIND logs refers to the IP address 172.16.10.16, can you tell us what is this
> IP?
> It appears that this is this IP address which is trying to transfer the zone,
> and as you are restricting zone transfers to the slave IP address
> (172.16.11.35),
Hi Lars,
On 26-Apr-2017 09:10 CEST, wrote:
> Am 26.04.2017 um 08:22 schrieb Steven Carr:
> > On 26 April 2017 at 06:53, Dr. Lars Hanke wrote:
> > > allow-transfer { 172.16.11.35; };
> > This IP ^^^
> >
> > > transfer of '178.168.192.in-addr.arpa/IN' from 172.16.10.16#53: failed
> > > while
>
Am 26.04.2017 um 08:22 schrieb Steven Carr:
On 26 April 2017 at 06:53, Dr. Lars Hanke wrote:
allow-transfer { 172.16.11.35; };
This IP ^^^
transfer of '178.168.192.in-addr.arpa/IN' from 172.16.10.16#53: failed while
receiving responses: REFUSED
Is not the same as the IP the AXFR request is
On 26 April 2017 at 06:53, Dr. Lars Hanke wrote:
> allow-transfer { 172.16.11.35; };
This IP ^^^
> transfer of '178.168.192.in-addr.arpa/IN' from 172.16.10.16#53: failed while
> receiving responses: REFUSED
Is not the same as the IP the AXFR request is coming from? ^^^
_
I have 2 Bind9.9.5 as of current Debian Jessie running is a Master/Slave
setup. Everything works fine, if I put
allow-transfer { 172.16/16; };
on the master. If I want to be more restrictive, i.e. specify the IP of
the slave immediatey
allow-transfer { 172.16.11.35; };
I see logs like
tran
6 matches
Mail list logo
