Closed bohemtucsok closed 1 year ago
what's the network setup like? is it 2 different machines?
do you have NS
records set correctly on the domain?
hi, yes, we are talking about two different vps servers, the ns records are set properly
powerdns may have some issues when dealing with NAT during zone transfers.. if possible, I would probably suggest to use network: host
for pdns and thus get rid of the NAT (if you want to keep master/slave replication)
alternatively, you can use replication on mysql level, and use NATIVE
type of zones in pdns
Hello, my problem is the following. I created the master server and set it up. This configuration works fine.
Then I created the slave server with this configuration
(master)
version: '2.2'
services: mariadb: image: mariadb networks: pdns: aliases:
mysql volumes:
pdns-master: image: pschiffe/pdns-mysql:${PDNS_MYSQL_TAG:-latest} hostname: ns5.xxxx.com networks: pdns: ipv4_address: 172.6.0.20 aliases:
pdns extra_hosts:
pdns-admin-uwsgi: image: pschiffe/pdns-admin-uwsgi networks: pdns: aliases:
pdns-admin-uwsgi volumes:
pdns-admin-static: image: pschiffe/pdns-admin-static networks:
networks: pdns: ipam: config:
volumes: mariadb:
The problem is imminent When the master server sends the axfr notify, the master server docker gateway ip appears in the log on the slave server and the process does not complete
(slave)
version: '2.2'
services: mariadb: image: mariadb networks: pdns: aliases:
mysql volumes:
pdns-slave: image: pschiffe/pdns-mysql:${PDNS_MYSQL_TAG:-latest} hostname: ns15.xxxxx.com networks: pdns: ipv4_address: 172.6.0.21 aliases:
networks: pdns: ipam: config:
volumes: mariadb:
This is the message:
Error resolving SOA or NS for xxxxx.com at: 172.6.0.1: Query to '172.6.0.1' for SOA of 'xxxxx.com' produced no answers
Does anyone have an idea what I messed up???