BIND 10 #3341: D2 should NOP updates in a given direction if no servers are defined for that direction

[BIND 10 Development]

#3341: D2 should NOP updates in a given direction if no servers are defined for
that direction
-------------------------------------+-------------------------------------
                   Reporter:  tmark  |                 Owner:
                       Type:         |                Status:  new
  defect                             |             Milestone:  DHCP-
                   Priority:         |  Kea0.9-alpha
  medium                             |              Keywords:
                  Component:  dhcp-  |             Sensitive:  0
  ddns                               |           Sub-Project:  DHCP
               CVSS Scoring:         |  Estimated Difficulty:  0
            Defect Severity:  N/A    |           Total Hours:  0
Feature Depending on Ticket:         |
        Add Hours to Ticket:  0      |
                  Internal?:  0      |
-------------------------------------+-------------------------------------
 Currently, if the direction flag for a given direction is true in a
 request (NCR), D2 will attempt to match the request to a suitable server.
 If no match is found, D2 will fail whole request.

 Change this logic to attempt the match only if there are servers defined
 for that direction.  If there are none, then D2 should treat updating in
 that direction as a NOP.

 This allow's the lack of servers defined in a given direction to treat
 updates in that direction as optional.  In other words, if we only define
 forward servers, requests which ask for both forward and reverse can still
 succeed, or vice-versa.

-- 
Ticket URL: <http://bind10.isc.org/ticket/3341>
BIND 10 Development <http://bind10.isc.org>
BIND 10 Development