BIND 10 #2005: DDNS documentation

[BIND 10 Development]

#2005: DDNS documentation
-------------------------------------+-------------------------------------
                   Reporter:         |                 Owner:  jinmei
  jinmei                             |                Status:  reviewing
                       Type:  task   |             Milestone:
                   Priority:  very   |  Sprint-20120619
  high                               |            Resolution:
                  Component:  DDNS   |             Sensitive:  0
                   Keywords:         |           Sub-Project:  DNS
            Defect Severity:  N/A    |  Estimated Difficulty:  6
Feature Depending on Ticket:  DDNS   |           Total Hours:  0
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
Changes (by jelte):

 * owner:  jelte => jinmei


Comment:

 Overall, it looks good. A few comments:

 In 'Enabling Dynamic Update' (around line 1950), I'd probably add a note
 that b10-xfrout is essentially required to run as well. If it is not
 running, b10-ddns will be in a coma for 4 seconds after each update
 (waiting for xfrout to not respond) (the note can include that we plan to
 change this in some way in the future).

 Around line 2074, the note about how update_acl must be set completely in
 one go is not entirely right; you can't add entries without value, but you
 can add entries one at a time if you specify the entry;
 {{{
 > config add DDNS/zones[0]/update_acl
 Error: No value given and no default for /DDNS/zones[0]/update_acl
 > config add DDNS/zones[0]/update_acl { "action": "ACCEPT", "key":
 "key.example.org", "from": "192.168.8.8" }
 > config add DDNS/zones[0]/update_acl { "action": "REJECT", "key":
 "key.example.org", "from": "192.168.9.9" }
 > config commit
 >
 }}}

 Line 2160: "There has to be no configuration to make this possible.", I'd
 rephrase that as "This is done automaticallyl; it does not require
 specific configuration to make this possible" (except of course that IXFR
 itself needs to be enabled). The current text implies that you have to
 explicitely not configure something.

 And about the manpage; not sure if we mention it for the other daemons,
 but -h is also a valid argument :)

 Assuming that there is not too much discussion on the above, I won't be
 able to look at it again, so you may merge after looking at these comments
 :)
 (otherwise you'll have to request someone else to take a look)

-- 
Ticket URL: <http://bind10.isc.org/ticket/2005#comment:6>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development