36 lines
985 B
Markdown
36 lines
985 B
Markdown
|
## DELEGATION07: Parent glue name records present in child
|
||
|
|
|
||
|
|
### Test case identifier
|
||
|
|
|
||
|
|
**DELEGATION07:** Parent glue name records present in child
|
||
|
|
|
||
|
|
### Objective
|
||
|
|
|
||
|
|
If the list of name servers for a domain obtained from its parent are not
|
||
|
|
found in its child zone, then it leads to an inconsistency (section 2.3
|
||
|
|
of [RIPE-114](https://www.ripe.net/publications/docs/ripe-114))
|
||
|
|
|
||
|
|
### Inputs
|
||
|
|
|
||
|
|
The domain name to be tested.
|
||
|
|
|
||
|
|
### Ordered description of steps to be taken to execute the test case
|
||
|
|
|
||
|
|
1. Obtain the complete set of name servers from the parent using
|
||
|
|
[Method2](../Methods.md) and the child using [Method3](../Methods.md).
|
||
|
|
3. If the set of NS names obtained from [Method2](../Methods.md) are
|
||
|
|
not found in [Method3](../Methods.md), then the test fails.
|
||
|
|
|
||
|
|
### Outcome(s)
|
||
|
|
|
||
|
|
If the set of glue name records obtained are found in the list of name
|
||
|
|
servers obtained from the child also, then the test succeeds
|
||
|
|
|
||
|
|
### Special procedural requirements
|
||
|
|
|
||
|
|
None
|
||
|
|
|
||
|
|
### Intercase dependencies
|
||
|
|
|
||
|
|
None
|