Replies: 1 comment
-
We had this same issue as well. Our setup had dnsdist running and forwarding requests to dns recursor and auth server running on same server as documented as scenario 2 in the docs. We noticed that the dig command would not pull back NS requests that contained the A records.
We had to update our dnsdist to have a rule that forced any queries coming from our secondary server to skip the recursor server. For some reason the recusror server would not reply back with the A records in the NS query response that the secondary pdns service was expecting. Changed... Once the dnsdist update was in place, the NS query was now routing to the pdns service instead of recusor service, and everything worked.
|
Beta Was this translation helpful? Give feedback.
-
Hi,
I'm attempting to setup a primary/secondary setup with the secondary being an autosecondary but running into an issue when attempting to notify the secondary zone.
Env info:
Primary:
d1.debug.com
192.168.100.50
Secondary:
d2.debug.com
192.168.100.51
Primary (
d1.debug.com
)Secondary (
d2.xes-test.com
)On the secondary server, d2.debug.com, I have an auto primary configured pointing to the IP of the primary server, with a NS of
d2.debug.com
.# pdnsutil list-autoprimaries IP=192.168.100.50, NS=d2.debug.com, account=
When sending a notify on the primary, I get the following error on the secondary.
Using dig, I've confirmed the nameservers exist and an A record exists as well.
Perhaps I'm missing something obvious but I cannot get this to function, any ideas?
Beta Was this translation helpful? Give feedback.
All reactions