Test scenarios for MethodsV2#1254
Conversation
b87c12a to
561aba3
Compare
…se test scenarios
…o be easier to work with
Co-authored-by: tgreenx <96772376+tgreenx@users.noreply.github.com>
* Updates to match updated specification where NXDOMAIN and NODAT for the tested domain is ignored. * Introduce a distinction between "empty" and "undefined" for some sets without members, e.g. set of parent NS IP.
|
|
||
|
|
||
|
|
||
| $ORIGIN parent ; Must be relative |
There was a problem hiding this comment.
Are relative domain names allowed in $ORIGIN directives? I doubt it, and I know nsd would reject such a directive.
There was a problem hiding this comment.
They are permitted. There is nothing in RFC 1035 forbidding the domain name after $ORIGIN. There is nothing special about the "" after $ORIGIN.
And CoreDNS has no problem with that. I pretty sure that also Bind supports it.
|
|
||
| ## Root hint for scenarios | ||
|
|
||
| For all scenarios the root hint should be |
There was a problem hiding this comment.
Just a minor cosmetic detail, but it feels more correct to name the root servers something like ns1.root-servers.xa instead of a TLD.
There was a problem hiding this comment.
It is nothing that could be changed here since that is part of the entire framework.
It does not disturb me, but having names with at least two labels before the final dot would work too, and it is more like you would expect. I can change it later in a PR that must be coordinated with a PR to Zonemaster-Engine too, and with a quick review and merge.
Co-authored-by: Marc van der Wal <103426270+marc-vanderwal@users.noreply.github.com>
matsduf
left a comment
There was a problem hiding this comment.
@marc-vanderwal, thank you for a thorough review into the details.
| * Zone: child.parent.chld-found-inconsist-6.methodsv2.xa | ||
| * Parent `ns1` has normal delegation of child to the two child NS. | ||
| * Parent `ns2` lacks delegation of child (NXDOMAIN). | ||
| * Child shares `ns1.parent.chld-found-inconsist-6.methodsv2.xa` with parent. |
There was a problem hiding this comment.
Yes, on parent ns1 (ns1.parent.chld-found-inconsist-6.methodsv2.xa).
| * Parent `ns1` has normal delegation of child to the two child NS. | ||
| * Parent `ns2` lacks delegation of child (NXDOMAIN). | ||
| * Child shares `ns1.parent.chld-found-inconsist-6.methodsv2.xa` with parent. | ||
| * Child also uses child `ns1` and `ns2`. |
There was a problem hiding this comment.
Child is also hosted on ns1 and ns2 (the default ns1 and ns2 for a child).
| other there is a NODATA response. | ||
|
|
||
| * Zone: child.parent.chld-found-inconsist-10.methodsv2.xa | ||
| * Parent `ns1` has normal delegation of child to two child NS, `ns1` and `ns2`. |
There was a problem hiding this comment.
Here "child" refer to the relation not the name. Both "child" and "parent" are used as relations here.
| * Normal response on grandparent `ns1`. | ||
| * Grandparent `ns2` responds with other owner name on NS query for | ||
| `zone-err-grandparent-3.methodsv2.xa`: | ||
| * Owner name `oncle.zone-err-grandparent-3.methodsv2.xa` instead. |
There was a problem hiding this comment.
I agree that "uncle" is the expected, but it is just a name. The name in the configuration is also "oncle". It should match.
|
|
||
|
|
||
|
|
||
| $ORIGIN parent ; Must be relative |
There was a problem hiding this comment.
They are permitted. There is nothing in RFC 1035 forbidding the domain name after $ORIGIN. There is nothing special about the "" after $ORIGIN.
And CoreDNS has no problem with that. I pretty sure that also Bind supports it.
|
|
||
| ## Root hint for scenarios | ||
|
|
||
| For all scenarios the root hint should be |
There was a problem hiding this comment.
It is nothing that could be changed here since that is part of the entire framework.
It does not disturb me, but having names with at least two labels before the final dot would work too, and it is more like you would expect. I can change it later in a PR that must be coordinated with a PR to Zonemaster-Engine too, and with a quick review and merge.
| Test zone specifications for the following methods are available (work in | ||
| progress): | ||
|
|
||
| [Get parent NS IP addresses](get-parent-ns-ip-addresses.md) |
There was a problem hiding this comment.
This link should be created, or removed.
| * [Undelegated data for scenarios](#undelegated-data-for-scenarios) | ||
| * [Data type in method output](#data-type-in-method-output) | ||
| * [Scenarios](#scenarios) | ||
| * [GOOD-1](#good-1) |
There was a problem hiding this comment.
This table should be updated with all scenarios.
Co-authored-by: tgreenx <96772376+tgreenx@users.noreply.github.com>
Purpose
This PR provides test scenarios for MethodsV2. They have been implemented in zonemaster/zonemaster-engine#1351.
How to test this PR
dig