-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Nameserver15 implementation #1218
Conversation
Edit: I have re-included that unitary test for now because I just moved the ones for Nameserver15 in a separate |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It works as excepted from what I can see.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor comments, but in general it looks fine, but I have to test too.
docs/logentry_args.md
Outdated
@@ -68,10 +68,12 @@ and updated messages (*msgids* and *msgstr*). | |||
| ns_list | List of domain name and IP address pairs | A list of name servers, as specified by "ns", separated by ";". | | |||
| nsname | Domain name | The domain name of a name server. | | |||
| nsname_list | List of domain names | A list of name servers, as specified by "nsname", separated by ";". | | |||
| query_name | Text | A query domain name (QNAME), as defined in [RFC1035, section 4.1.2]. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is text in the same way as nsname
is text, but the latter is restricted text. I think it is better to say that it is a Domain name
. Another possibility is to say that the argument is a domain
and do not define a new argument name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated
docs/logentry_args.md
Outdated
| rcode | An RCODE Name | An RCODE Name (not numeric code) from [DNS RCODEs]. | | ||
| rrtype | A Resource Record TYPE Name | A Resource Record TYPE Name (not numeric code) from [DNS RR TYPEs]. | | ||
| soaserial | Non-negative integer | The numeric value for the SERIAL field in an SOA record. Integer in range 0-4,294,967,295 | | ||
| soaserial_list | List of non-negative integers | A list of non-negative integers, as specified by "soaserial", separated by ";". | | ||
| string | Text | The content of the RDATA of a TXT ressource record. | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"resource" is misspelled.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
docs/logentry_args.md
Outdated
@@ -149,5 +151,6 @@ Message names maked with a question mark should not be considered stable. | |||
[DNSSEC algorithm]: https://www.iana.org/assignments/dns-sec-alg-numbers/dns-sec-alg-numbers.xhtml | |||
[DS Digest algorithm]: https://www.iana.org/assignments/ds-rr-types/ds-rr-types.xhtml | |||
[fr.po]: ../share/fr.po | |||
[RFC1035, section 4.1.2]: https://datatracker.ietf.org/doc/html/rfc1035#section-4.1.2 | |||
[sv.po]: ../share/fr.po |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you fix the typo here (not from this PR): ../share/fr.po
--> ../share/sv.po
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fixed
Purpose
This PR proposes an implementation of the newly specified Nameserver15 Test Case.
Context
zonemaster/zonemaster#1150
Changes
lib/Zonemaster/Engine/Test/Nameserver.pm
+profile.json
docs/logentry_args.md
t/Test-nameserver15.t
+t/Test-nameserver15.data
How to test this PR
Unit tests should pass. All message tags are covered, however note that they are not using "controlled" zones.
Also: