mirror of
https://github.com/PowerDNS-Admin/PowerDNS-Admin.git
synced 2026-04-25 08:45:55 +03:00
[GH-ISSUE #13] Support for PowerDNS 4.x #10
Labels
No labels
bug / broken-feature
bug / broken-feature
docs / request
feature / request
help / other
mod / help-wanted
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/PowerDNS-Admin-PowerDNS-Admin#10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @TacoScheltema on GitHub (Mar 13, 2016).
Original GitHub issue: https://github.com/PowerDNS-Admin/PowerDNS-Admin/issues/13
Hi,
Will you be supporting PowerDNS 4.x? I got it to work nicely on version 3 but on 4 I can only see the domains, not the records under a domain (I get a 500 error then).
Cheers,
Taco
@ngoduykhanh commented on GitHub (Mar 17, 2016):
PowerDNS 4 still in Alpha release. But I will start working on this to make sure PowerDNS-Admin can work with the new version of PowerDNS.
@Trozz commented on GitHub (Apr 28, 2016):
any movement on this?
@ivanfilippov commented on GitHub (May 6, 2016):
I've started a very naive implementation of pdns 4 support in a new branch. You'll need to add
/api/v1/to the end of your PDNS_STATS_URL inconfig.pywhen configuring the new code.It works in my test environment with pdns 4.0.0-alpha1, but I would appreciate feedback from others.
The branch can be found here: https://github.com/ivanfilippov/PowerDNS-Admin/tree/pdns4-support
@ivanfilippov commented on GitHub (May 15, 2016):
Spoke too soon, this will need quite a bit more work to work properly with pdns4.
@ngoduykhanh commented on GitHub (Jun 7, 2016):
@ivanfilippov : I've pushed some adjustments to support pdns v4.x.x in our
new_uibranch.Features are working:
Still have problem with multiple records adding which described at https://github.com/ngoduykhanh/PowerDNS-Admin/issues/5#issuecomment-181637576 in my adjustment.
Let me know if you have any idea/adjustment.
@ivanfilippov commented on GitHub (Jun 8, 2016):
@ngoduykhanh I fixed the multiple record adding issue in this commit:
github.com/ivanfilippov/PowerDNS-Admin@812aa055f8During testing I noticed that the new PDNS API won't accept MX or SRV records unless they are suffixed by a '.'. This looks like it's part of the spec for MX and SRV records, so I'll work on adding that in as well just for the new API code.
@ivanfilippov commented on GitHub (Jun 8, 2016):
@ngoduykhanh I fixed the '.' issue with MX and SRV records I mentioned above, but I'm not sure that the way I fixed it is the best way. Can you review it? Commit here:
github.com/ivanfilippov/PowerDNS-Admin@b9f57e8cfe@ngoduykhanh commented on GitHub (Jun 8, 2016):
@ivanfilippov : I am OK with your change. But it looks like we need more than
MXandSRVhere.CNAME,NSalso requires trailing dot in their content.p/s: pdns v4.x.x requires to add a trailing dot in the records
nameandcontent, but the trailing dots aren't saved in the pdns's database actually :)@ivanfilippov commented on GitHub (Jun 8, 2016):
@ngoduykhanh I noticed that the pdns database does not save the dots as well, but pdns itself must add them when responding to queries. I wonder why they decided to do that.
We'll need to add CNAME and NS to this line:
github.com/ivanfilippov/PowerDNS-Admin@b9f57e8cfe (commitcomment-17781503)Go ahead and add those two in if you're free, I won't have a chance to look at it until tomorrow. 😄
@ngoduykhanh commented on GitHub (Jun 8, 2016):
@ivanfilippov : I see. I will take care of adding those two in. thanks Ivan.
@ngoduykhanh commented on GitHub (Jun 8, 2016):
Pushed commit
aad9d92038for those changes.@ivanfilippov commented on GitHub (Jun 8, 2016):
@ngoduykhanh
Thanks!
By the way, I'm going to remove my own
new_uibranch and push directly to the one in your repo, having my own branch and keeping it in sync is becoming a pain. 😄@ngoduykhanh commented on GitHub (Jun 8, 2016):
@ivanfilippov
Yes, you should do that. Thanks buddy :)
@ngoduykhanh commented on GitHub (Jun 26, 2016):
PDNS 4.x.x is supported now with PR #50 . Feel free to open issues related to PDNS 4.x.x compatibilities.