[Pdns-users] Master/Slaves in docker containers

[frank+pdns at tembo.be]

Hi Christian,

> pdns master is running on host 192.168.213.11, and container ip is 172.17.0.4
>  
> pdns slave is running on host 192.168.213.12, and container ip is 172.17.0.3
>  
> both containers have gateway set to 172.17.0.1, and hosts have gateway set to 192.168.213.1
>  
> Both containers publishes udp/53 and tcp/53  (as 0.0.0.0:53) so basically, I can connect to any of these two, targetting the 192.168.213.x IP
>  
> But when I do a zone update on the master container, docker logs of the pdns-slave shows these two things, for all the domains for which he should be authoritative:
> 
> - Received NOTIFY for _this_particular_zone_ from 172.17.0.1 for which we are not authoritative
> - Error resolving SOA or NS for _this_particular_zone_ at: 172.17.0.1: Query to '172.17.0.1' for SOA of '_this_particular_zone_' produced no answer
> 

Could you do the following:

- start a tcpdump on pdns-slave
- from pdns-master: do a dig something @192.168.213.12
- from pdns-master: trigger a notify to 192.168.213.12

And show us the tcpdump?



Frank


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20190529/d4909872/attachment.html>