Reverse doesn't work in this config, so I figure on giving up on
recursor.
An auth ns was my goal, so I am happy that pdns works forward and
reverse, and poweradmin makes it easy to manage.
I can either use my router's recursor, or perhaps set up a pdns-
recursor on a different VM to keep it
OK, I managed to get DiG to respond with A records, but only by
specifying the hostname in from of the domain name. This is OK, but
when the servers where reversed, a simple DiG NS would return the NS
records, *and* the A records.
Again not a showstopper unless it points to config still broken.
Well, I managed to reverse the servers, and get them working.
DiG now works for +trace.
The auth server also seems to be working.
One new quirk:
DiG to my domain NS sends back the NS records but not the A records,
whereas all records came back when the auth server was on top.
But the auth
Thanks for the quick reply.
Yes, I did see this info at one point, and so I tried briefly to run
the recursor in front on its own, but I have not got it working yet.
Also,I did try the auth pdns as a recursor itself as I figured it
should work as an integrated server. But, I got the exact same
On 2017-02-16 6:29 PM, stancs3 wrote:
I have seen this problem posted in various places over the years. It is
not clear if it is a bug, a bad config, or just non-functional.
https://github.com/PowerDNS/pdns/issues/4353
In your case (auth pointing to recursor) is a fairly broken config to
I have seen this problem posted in various places over the years. It is
not clear if it is a bug, a bad config, or just non-functional.
My set up:
VM running Centos 7, up to date.
pdns install using postgresql db.
pdns-recursor install.
pdns is running as an authoritive ns, standalone,
I'm with David,
2 recursion services on the same server?
I would also stop the recursor on the auth service and set the recursor to
forward the queries to your "domains in auth server" directly to it using "
forward-zones=" on the recursor side.
Ale
-Original Message-
From:
