auth_badzone.feature 1.6 KB

12345678910111213141516171819202122232425262728293031323334353637
  1. Feature: Authoritative DNS server with a bad zone
  2. This feature set is for testing the execution of the b10-auth
  3. component when one zone is broken, whereas others are fine. In this
  4. case, b10-auth should not reject the data source, but reject the bad
  5. zone only and serve the good zones anyway.
  6. Scenario: Bad zone
  7. Given I have bind10 running with configuration auth/auth_badzone.config
  8. And wait for bind10 stderr message BIND10_STARTED_CC
  9. And wait for bind10 stderr message CMDCTL_STARTED
  10. And wait for bind10 stderr message AUTH_SERVER_STARTED
  11. bind10 module Auth should be running
  12. And bind10 module Resolver should not be running
  13. A query for www.example.org should have rcode NOERROR
  14. The last query response should have flags qr aa rd
  15. The last query response should have ancount 1
  16. The last query response should have nscount 2
  17. The last query response should have adcount 2
  18. The answer section of the last query response should be
  19. """
  20. www.example.org. 3600 IN A 192.0.2.1
  21. """
  22. The authority section of the last query response should be
  23. """
  24. example.org. 3600 IN NS ns1.example.org.
  25. example.org. 3600 IN NS ns2.example.org.
  26. """
  27. The additional section of the last query response should be
  28. """
  29. ns1.example.org. 3600 IN A 192.0.2.3
  30. ns2.example.org. 3600 IN A 192.0.2.4
  31. """
  32. A query for www.example.com should have rcode REFUSED