BIND 10 #1460: Define system-level tests for DDNS

[BIND 10 Development]

#1460: Define system-level tests for DDNS
-------------------------------------+-------------------------------------
                   Reporter:  jelte  |                 Owner:  jelte
                       Type:  task   |                Status:  reviewing
                   Priority:         |             Milestone:
  medium                             |  Sprint-20120612
                  Component:  DDNS   |            Resolution:
                   Keywords:         |             Sensitive:  0
            Defect Severity:  N/A    |           Sub-Project:  DNS
Feature Depending on Ticket:  DDNS   |  Estimated Difficulty:  5
        Add Hours to Ticket:  0      |           Total Hours:  6
                  Internal?:  0      |
-------------------------------------+-------------------------------------

Comment (by jinmei):

 A couple of more BIND 10 specific things:

 - It's worth testing what happens b10-ddns once started but stops
   running, then restarts again.  update requests will have to be
   forwarded to and processed by b10-ddns after restart.  Note that the
   first request after restart will probably fail with SERVFAIL because
   b10-auth still keeps the socket with the now-stale connection, and
   it can only detect the failure in the next push() operation (#1986
   could solve this)
 - Likewise, we should check the behavior when b10-auth dies (and
   restarts) after establishing a connection with b10-ddns.  That's
   apparently the scenario that makes xfrout fall into a busy loop.
   The smarter socket session library and the way b10-ddns uses it
   should avoid the bug, but we need to check.

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