Primary/Secondary servers on different hosts with Podman failing AXFR/Notify #15378
Unanswered
rheaalleen
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hi,
I was experimenting with the container images from pschiffe/powerdns to get a cluster running. However with rootless podman I was unsuccessful so far when I split the primary/secondary to different hosts.
Running the primary/secondary on a single host was easy since I can attach the same network and define static IPs. After setting the NS/A records through PowerDNS-Admin I was seeing the Notify/AFXR.
However splitting the services to different hosts was unsuccesful. When triggering a manual notify-host from the primary the secondary it gets the error. The same configuration that was working now has problems because of the networking.
It's seeing its own IP as allow-notify source IP, switching the
PDNS_allow_notify_from: '{{ pdns_master_ip }}'
toPDNS_allow_notify_from: '{{ pdns_master_ip }}'
in the secondary configuration changes the error message toThe messages arrive with their internal podman network IP and I didnt see any way to use the host IP.
Anything else, for the primary works, I can set records, query them with the defined IP:Port, just the communication for AXFR/Notify wont work.
Before setting the container IPs as ns1/2 records inside the containers /etc/hosts I had the server IPs which resulted in the same error
Trimmed configuration for both services/hosts
Secondary on Host B
Primary on Host A
Beta Was this translation helpful? Give feedback.
All reactions