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
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
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
Following the last Debian Jessie update, my Samba attached bind ceased
working. Since there was no Samba update, the DLZ libs were unchanged,
as was the configuration.
I'm now running BIND 9.9.5-7-Debian, which imports zones from a Samba4
installation. Actually, Samba is expected to only serve
I have a Bind9 infrastructure serving an internal network at .mytld.
Since it may happen that .mytld becomes an official TLD in the future, I
decided to migrate to .internal.my.official.tld, i.e. currently all
machines are available with the same IP in both domains.
Now we decided to move our
5 matches
Mail list logo
