xfrin_notify_handling.feature 1.5 KB

1234567891011121314151617181920212223242526272829
  1. Feature: Xfrin incoming notify handling
  2. Tests for Xfrin incoming notify handling.
  3. Scenario: Handle incoming notify
  4. Given I have bind10 running with configuration xfrin/retransfer_master.conf with cmdctl port 47804 as master
  5. And wait for master stderr message BIND10_STARTED_CC
  6. And wait for master stderr message CMDCTL_STARTED
  7. And wait for master stderr message AUTH_SERVER_STARTED
  8. And wait for master stderr message XFROUT_STARTED
  9. And wait for master stderr message ZONEMGR_STARTED
  10. And I have bind10 running with configuration xfrin/retransfer_slave_notify.conf
  11. And wait for bind10 stderr message BIND10_STARTED_CC
  12. And wait for bind10 stderr message CMDCTL_STARTED
  13. And wait for bind10 stderr message AUTH_SERVER_STARTED
  14. And wait for bind10 stderr message XFRIN_STARTED
  15. And wait for bind10 stderr message ZONEMGR_STARTED
  16. A query for www.example.org to [::1]:47806 should have rcode NXDOMAIN
  17. When I send bind10 with cmdctl port 47804 the command Xfrout notify example.org IN
  18. Then wait for new master stderr message XFROUT_NOTIFY_COMMAND
  19. Then wait for new bind10 stderr message AUTH_RECEIVED_NOTIFY
  20. Then wait for new bind10 stderr message ZONEMGR_RECEIVE_NOTIFY
  21. Then wait for new bind10 stderr message XFRIN_XFR_TRANSFER_STARTED
  22. Then wait for new bind10 stderr message XFRIN_TRANSFER_SUCCESS not XFRIN_XFR_PROCESS_FAILURE
  23. Then wait for new bind10 stderr message ZONEMGR_RECEIVE_XFRIN_SUCCESS
  24. A query for www.example.org to [::1]:47806 should have rcode NOERROR