Submitted by reachoneinternet on Tue, 01/18/2011 - 12:24
I think there's a bug in the PowerDNS plugin in that it fails to update the SOA record when updating an existing zone. In addition, there seems like there's room for improvement in sanity checking (for example limiting the delete query to one domain record) etc.
Who is maintaining this package? I wouldn't mind helping out...
-Christopher Hunt ReachONE Internet chunt@reachone.com
Status:
Closed (fixed)
Comments
Submitted by JamieCameron on Tue, 01/18/2011 - 14:51 Comment #1
I am maintaining it, although it isn't very heavily used as most Virtualmin users run BIND.
What goes wrong with the SOA record exactly?
Submitted by reachoneinternet on Tue, 01/18/2011 - 15:29 Comment #2
the SOA record simply isn't touched, even when IP changes and the relevant A records are updated. The lack of an SOA record update also means a potentially big delay in propagation of updates. Plus, the "add" routine it uses an initial serial of "0" (or whatever static value is in the template) which, although RFC-compliant i think, isn't very useful. I'd like to see a serial based on date/time for the "add" routine and the edits too, although a rule which merely increments the serial would suffice.
-chris
Submitted by JamieCameron on Tue, 01/18/2011 - 15:49 Comment #3
Ah, OK .. I will fix those issues in the next release of the powerDNS plugin. Let me know if you'd like a pre-release version.
Submitted by Issues on Tue, 02/01/2011 - 16:20 Comment #4
Automatically closed -- issue fixed for 2 weeks with no activity.