Hi

Maybe someone could help me..

I try to setup bind 9.11 with webmin as DNS with different views for two networks.

Default zones 0, 127, 255, localhost (all In view called "ViewRoot" - Default) can transfer without problems to my slave Host (same Bind and Webmin version).

New Master Zone blubb.lan (In view "View172" - limited to 172.20.76.0/22) cannot transfer to slave host:

Logs on master:
15-Jan-2019 11:54:45.164 xfer-out: info: client @0x7fc5200f30b0 172.20.76.8#36991 (blubb.lan): view ViewRoot: bad zone transfer request: 'blubb.lan/IN': non-authoritative zone (NOTAUTH)

Logs on slave:
Jan 15 11:22:09 webmin-slave named[1220]: zone blubb.lan/IN/View172: refresh: non-authoritative answer from master 172.20.76.7#53 (source 0.0.0.0#0)

Can anyone help me? Thanks in advance!

Jan


named.conf.local

According to the logs above, looks like the secondary is trying to transfer the zone blubb.lan from master's view ViewRoot (the 1st view), and the master respond that it's not authoritative for that zone in that view.
This is typical when you use views and try to update zones between master-slave without using keys.

I don't know how webmin dns setup works, but you can take a look here to see what you have to do in bind config. Then configure webmin accordingly.


Regards

Hi bathory,

thank you very much for the tipp. You pushed me into the right direction.
First, i had to understand that for the transfer of the records, the view has to be matched by the slave. My View172 is limited to 172.20.76.0/22, so the slave has to start the transfer from an ip within 172.20.76.0/22.

My next problem was the order of the views. First view in /etc/bind/named.conf.local was "ViewRoot" without limitation to clients. So my connection from the slave was routed to ViewRoot everytime. I have changed the order of views and now it works.

Best regards
Jan