Feature: In-memory zone using SQLite3 backend
    This feature tests the authoritative server configured with an in-memory
    data source that uses the SQLite3 data source as the backend, and tests
    scenarios that update the zone via incoming zone transfers.

    Scenario: 1. Load and response
        Given I have bind10 running with configuration inmemory_over_sqlite3/secondary.conf
        And wait for bind10 stderr message BIND10_STARTED_CC
        And wait for bind10 stderr message CMDCTL_STARTED
        And wait for bind10 stderr message AUTH_SERVER_STARTED
        A query for www.example.org should have rcode NOERROR
        The SOA serial for example.org should be 1234

    Scenario: 2. In-memory datasource backed by sqlite3
        Given I have bind10 running with configuration xfrin/retransfer_master.conf with cmdctl port 47804 as master
        And wait for master stderr message BIND10_STARTED_CC
        And wait for master stderr message CMDCTL_STARTED
        And wait for master stderr message AUTH_SERVER_STARTED
        And wait for master stderr message XFROUT_STARTED
        And wait for master stderr message ZONEMGR_STARTED

        And I have bind10 running with configuration xfrin/inmem_slave.conf
        And wait for bind10 stderr message BIND10_STARTED_CC
        And wait for bind10 stderr message CMDCTL_STARTED
        And wait for bind10 stderr message AUTH_SERVER_STARTED
        And wait for bind10 stderr message XFRIN_STARTED
        And wait for bind10 stderr message ZONEMGR_STARTED

        A query for www.example.org to [::1]:47806 should have rcode NOERROR
        """
        www.example.org.        3600    IN      A       192.0.2.63
        """
        A query for mail.example.org to [::1]:47806 should have rcode NXDOMAIN
        When I send bind10 the command Xfrin retransfer example.org IN ::1 47807
        Then wait for new bind10 stderr message XFRIN_TRANSFER_SUCCESS not XFRIN_XFR_PROCESS_FAILURE
        Then wait for new bind10 stderr message AUTH_LOAD_ZONE

        A query for www.example.org to [::1]:47807 should have rcode NOERROR
        The answer section of the last query response should be
        """
        www.example.org.        3600    IN      A       192.0.2.1
        """
        A query for mail.example.org to [::1]:47806 should have rcode NOERROR
