In order to understand user requirements for DDNS, a multi pronged user needs assessment and user story collection effort was started. 25 user survey respondents who market DDNS as "critical" to their BIND use will be queried as a user group.

Initial set of user stories:

Please be conservative & modular with features. If I don't want something (say dynamic DNS), then I should be able to run without it. Ticket #1466

"[I need] for dynamic updates [to take] less time to configure" Ticket #1474

"[I need there to be]less issues when running [DDNS] alongside Samba4" Ticket #1475

"[I need] Analysis tools that could aid me in getting more data on what is really going on in our systems. For example, I have a problem that I'm trying to figure out and do not have the tools, or do not know where to find access to what is happing in the "right now" interaction of our DNS with our DHCP and DDNS other than trying to read logs that fly by." Ticket #1465

"I need some way to go through DNS and find inactive DDNS machines." Ticket #1473

Need interoperability with Microsoft ADDNS Ticket #1476

Need DDNS with TSIG Ticket #1477

Views and dynamic updates to specific view. Ticket #1480

Dynamic updates journal should really become crash-safe. Ticket #1479

rate of dynamic updates DNSSEC with dynamic updates is very high for us, need configuration parameters to customize for this and logging to track it Ticket #1478

Data for future:

From user interviews November 2011:

DHCPD updates DNS (a single zone)

All Clients update another zone via nsupdate (here a scalable solution for the key management problem would help. Currently I have only one key distributed to 60.000 Clients.) - need to discuss more with user (cchen)

The deployment procedures for servers in our data centers make use of DDNS.

My dream feature for DDNS would be a server feature to define triggers on incoming DDNS updates. E.g. an update for ([a-z0-9]+) induces the DNS-Server to call a configured procedure like "update add $ $srcIP_of_packet" and/or "update add $ 60 txt $TIMESTAMP" - we will do this one in the future.

Last modified 8 years ago Last modified on Dec 6, 2011, 12:57:30 PM