CONSISTENCY03
All SOA record timer fields must be consistent across all authoritative name servers. An inconsistency in these fields might result in operational inconsistencies for the designated zone.
There are other test cases that provide consistency tests for the other SOA fields:
- CONSISTENCY01 (SOA Serial)
- CONSISTENCY02 (RNAME)
- CONSISTENCY06 (MNAME)
It is assumed that Child Zone is also tested by Connectivity01. This test case will set DEBUG level on messages for non-responsive name servers.
- The domain name to be tested ("Child Zone").
-
Create an SOA query for Child Zone apex.
-
Obtain the list of name server IPs for the Child Zone from Method4 and Method5.
-
Send the SOA query to all name server IPs.
-
If a name server does not respond, emit NO_RESPONSE.
-
If a name server responds but no SOA record is included in the response, emit NO_RESPONSE_SOA_QUERY.
-
Retrieve the SOA RR from the responses from all name server IPs.
-
Emit ONE_SOA_TIME_PARAMETER_SET if at least one SOA record has been retrieved and all SOA records have:
- the same REFRESH value,
- the same RETRY value,
- the same EXPIRE value, and
- the same MINIMUM value.
-
Emit MULTIPLE_SOA_TIME_PARAMETER_SET if any two SOA records had different values in previous step.
The outcome of this Test Case is "fail" if there is at least one message with the severity level ERROR or CRITICAL.
The outcome of this Test Case is "warning" if there is at least one message with the severity level WARNING, but no message with severity level ERROR or CRITICAL.
In other cases the outcome of this Test Case is "pass".
| Message | Default severity level (if message is emitted) |
|---|---|
| NO_RESPONSE | DEBUG |
| NO_RESPONSE_SOA_QUERY | DEBUG |
| ONE_SOA_TIME_PARAMETER_SET | INFO |
| MULTIPLE_SOA_TIME_PARAMETER_SET | NOTICE |
If either IPv4 or IPv6 transport is disabled, ignore the evaluation of the result of any test using this transport protocol. Log a message reporting on the ignored result.
None.