Suggestion: use PowerDNS API rather than modifying the backend DB

[revellion]

I would like to suggest looking at PowerDNSs API instead of modifying the DB in the backend. This might prove more stable/robust?

[Rico29]

I think it's a good suggestion too. The way it's actually implemented is not usable for production environment, too much "bugs".

[Kvaksrud]

+1

[mrlesmithjr]

I agree with this as well. The biggest reason that I have which confirms using the API would be the best bet is when managing a Master/Slave PowerDNS setup in which AXFR transfers need to occur. Directly manipulating the DB does not trigger a change therefore any new records and etc. do not transfer. Direct DB manipulation works fine for Native zones being that the back-end DB takes care of the replication. Certain use cases do not allow for Native zones however.

[mrlesmithjr]

After doing some additional testing the above comment that I made is not 100% accurate. After setting per domain the following it seems to work...So maybe have an option similar to autoserial allowing for setting domainmetadata options???? Just a thought.

mysql> select * from powerdns.domainmetadata;
+----+-----------+--------------+---------------------+
| id | domain_id | kind | content |
+----+-----------+--------------+---------------------+
| 1 | 1 | SOA-EDIT-API | INCEPTION-INCREMENT |
| 2 | 2 | SOA-EDIT-API | INCEPTION-INCREMENT |
| 3 | 3 | SOA-EDIT-API | INCEPTION-INCREMENT |
| 4 | 4 | SOA-EDIT-API | INCEPTION-INCREMENT |
| 19 | 19 | SOA-EDIT-API | INCEPTION-INCREMENT |
+----+-----------+--------------+---------------------+

[sid3windr]

This was also suggested by me in #302 which was subsequently closed; any progress? phpIPAM is creating wrong zones, like it creates a 10.in-addr.arpa zone to put 10.12.5.x DNS into, even though 5.12.10.in-addr.arpa zone already exists. PowerDNS API would handle this fully transparently. (disclaimer, likely not on latest trunk, but still...)

Thanks!

[bartmeuris]

Any news on this? Direct DB manipulation using MariaDB/MySQL is a non-starter since I use another database backend. Using the API would prevent a lot possible issues, and allow using any backend in PowerDNS that's supported by it's API.

[sid3windr]

It would also solve an issue where for me, phpIPAM s creating records in the wrong zone (I have /24 NS delegations for something in 10.0.0.0/8, which phpIPAM is creating in the 10.in-addr.arpa zone instead).

[blakkheimgw]

I'm also looking after this feature !

[Ron9DK]

I'm also looking forward for this feature to be implemented.

[HiTm4n]

Hello
This feature would be awesome !

[sbeccato]

Are there any updates on this?
Direct DB manipulation is not a great idea but using API yes!

I would like to connect my phpIPAM to my Powerdns infrastructure but not with direct db manipulation.

Someone have news?

[exeral]

I think PowerDNS API calls should integrated using this feature #880

[dtoubelis]

I'm interested in this feature as well. Manipulating the database directly:

• limits it to MySQL backend only
• bypasses validation of the record format (for example phpipam allows the creation of multiple TXT records for apex domain which API could have prevented..., phpipam sets the priority on records that does not support priority, i.e. NS, CAA, CNAME, TXT, SRV, etc... and the list goes on...)
• phpipam sometimes creates duplicate records when changing domain name of the host...
• does not always trigger server refresh and require zone "rectification" if pdns detects that sone serial haven't been updated properly (which is optional in phpipam)
• incompatible with pdns 4.3+ schema, which would be non-issue if API approach is used...

All these problems can be fixed in one go by switching to using API. The Pdns API is pretty stable these days, well documented and well maintained, so this would also assure compatibility with future versions of pdns.

So, pretty please... :-)

[longhtran91]

Is this still part of the roadmap?