Feature Requests Tracking

[jbe-dw]

Hello Community,

We said we would do some cleaning in the tickets. One thing we want to do is keep track of opened feature requests in the tracker. To be clear as water we will reference closed feature request tickets in this post.

When we will have time to work on them, we will state on what is coming and what is not accepted.
Feel free to work on any Feature you're missing and submit PR meanwhile (but remember that it may be delayed until we will have cleared the current task queue).

Regards

---

1 Password reset option
2 Show number of current changes beside "Apply" button in zone edition
3 PDA UI customization improvements
4 Improve PRETTY_IPV6 compatibility with wildcard record
5 Add option for reading custom header for /nic/checkip.html
6 Import bind standard zone file
7 Edit template name and description
8 Add a button to refresh all slave domains from the dashboard
9 Ability to clone a domain
10 Manage domain metadata (like TSIG-ALLOW-DNSUPDATE or TSIG-ALLOW-AXFR)
11 Use language package
12 set default zone type
13 Restrict Domain Templates to a User
14 Feature request : Dynamic templates
15 Managing multiple PowerDNS Servers with single PDNS-Admin instance
16 Automatic update DS key on DNSSEC enable
17 Feature Request: Add domain content version control
18 Export / Import features
19 Feature request: reapply template to a domain
20 auto_ptr setting should give option to NOT create zones
21 Feature Request: Support multiple ldap backends
22 Feature Request: Smart domain sort in Dashboard (sort by domain level)
23 Feature request: Customizable Logo and Title
24 Feature Request: Add a validation step before actually enabling 2FA
25 Feature Request: Allow short names for CNAME in the GUI
26 Feature Request: Add LDAP startTLS option
27 Feature Request: External Provider avatar support
28 [feature] Display current SOA-EDIT-API setting in zone admin page
29 Feature Request: Description column for each Basic Settings
30 Feature Request: Add a configuration API endpoint with initial admin and/or apikey setup

[jbe-dw]

40 [feature] Make it possible to set "auto ptr" per record creation
41 [feature] Make Disabled records more visual
42 Feature Request: Bulk domain creation with a template
43 Feature Request: Ability to set a default account for users automatically applied to domains
44 Feature Request: Improve Auto-PTR Option
45 Feature Request: Ability to configure natively PDA under a subdirectory
46 Feature Request: Provide an easier method for deployment (packages or ansible)
47 Feature Request: move the record helper from a universal value to a per-user option
48 Feature Request: Support OpenLDAP nested group membership
49 Feature request: Allow Multi Arch Docker Support (arm64)
50 Feature Request: Allow DynDNS API to update TXT records
51 Feature Request: Add Templates placeholder for domain name
52 Feature Request: Allow posixGroup support in LDAP GROUP SECURITY
53 Feature Request: CockroachDB support
54 Feature Request: Automatically generete a user/password for dyndns usage
55 Apply template to existing domain zone
56 Bulk delete records from zone
57 [Feature request] Support for GeoIP backend
58 Add support to configure SLAVE-RENOTIFY per zone
59 Support SVCB / HTTPS Types

[jbe-dw]

Reserved

[jbe-dw]

Reserved

[Heshmatkhah]

Hi
Are there any updates for managing domain metadata (specially TSIG, TTL)?

[metrax]

59 No support APL record type #1287

[AzorianMatt]

Hi Are there any updates for managing domain metadata (specially TSIG, TTL)?

@Heshmatkhah At this time, I can not give you any delivery timing expectations, but I can tell you that more advanced management features are being planned that will fully address domain metadata as well as targeted features for managing TSIG registrations.

[almereyda]

Coming here from

• [feature] Make Disabled records more visual #770

and seeing this is a known feature request. Unfortunately from the list of closed sub-issues, it is not immediately visible to me, which of those are going to be considered, declined, and which would already be implemented.

I'm suggesting to convert the numbered list of links to issues to what GitHub calls a 'task list'.

• About task lists - GitHub Docs

For the three suggested states accepted, declined and resolved one could use such notation

- [ ] #770
- [ ] ~~#770~~
- [x] #770

to generate a list like

• [feature] Make Disabled records more visual #770
• [feature] Make Disabled records more visual #770
• [feature] Make Disabled records more visual #770

This particular feature could be marked as resolved, as it appears to be implemented by the time being:

[alsyundawy]

req ipv4 /24 & ipv6 /64 ptr record generator

[metrax]

@alsyundawy
Please read: #1459