BIND 10 #1298: don't do xfrin upon notify when address is unknown

[BIND 10 Development]

#1298: don't do xfrin upon notify when address is unknown
-------------------------------------+-------------------------------------
            Reporter:  jelte         |                        Owner:
                Type:  defect        |                       Status:  new
            Priority:  major         |                    Milestone:  New
           Component:  Unclassified  |  Tasks
           Sensitive:  0             |                     Keywords:
         Sub-Project:  DNS           |              Defect Severity:  N/A
Estimated Difficulty:  0             |  Feature Depending on Ticket:
         Total Hours:  0             |          Add Hours to Ticket:  0
                                     |                    Internal?:  0
-------------------------------------+-------------------------------------
 right now, if xfrin gets a notify command (signaling that a notify packet
 has been received), it'll look up the master address and perform transfer.
 We should probably check the address the notify came from, and only do the
 transfer if it matches the address in the configuration.

 This has the side-effect of making the notify-self problem (#965) less
 bad, as it will still notify, but won't act upon it (this is probably also
 the cause of #988)

 It is also more as specified in the RFC (except we can only configure one
 master address right now)

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