Skip to content

Updated test case Zone09#870

Merged
matsduf merged 16 commits into
zonemaster:developfrom
matsduf:update-zone09
Jul 21, 2022
Merged

Updated test case Zone09#870
matsduf merged 16 commits into
zonemaster:developfrom
matsduf:update-zone09

Conversation

@matsduf

@matsduf matsduf commented Jul 4, 2020

Copy link
Copy Markdown
Contributor

Re-written test case Zone09

  • Added exception for root zone, TLDs and zones under .ARPA to be required (expected) to have MX.
  • Updated the steps to be explicit.
  • Updated the steps to cover all name servers for the zone.
  • Added explicit messages.
  • Ignored address records (A/AAAA) from being mail domain target.
  • Considered "Null MX"
  • Assumes that Basic04 is run and disregard basic name server problems.

This PR will resolve issue #841 and include some validation of "Null MX" (issue #754).

Further updates:

When this update has been merged, the implementation must also be updated.


Updates 2022-07-15

The PR was rebased on latest develop branch. All commits before 12085c1 are the same changes that were done 2022-01-17 and earlier.

Added updates:

  • Adds reference to "Query and responds defaults".
  • Updates the message tags to make them shorter.
  • Updates the message tag table to make it follow proposed
    updates to the specification template.
    • Adds message ID
    • Adds arguments to message ID
  • Editorial updates.

@matsduf matsduf added the A-TestCase Area: Test case specification or implementation of test case label Jul 4, 2020
@matsduf matsduf added this to the v2020.1 milestone Jul 4, 2020
@matsduf matsduf linked an issue Jul 4, 2020 that may be closed by this pull request
@cgsecurity

Copy link
Copy Markdown

Should Z09_ARPA_MAIL_DOMAIN_NOT_REQUIRED and Z09_TLD_MAIL_DOMAIN_NOT_REQUIRED be INFO or WARNING ?

Maybe tests should be added to report Z09_NULL_MX_FOUND_WITH_NON_ZERO_PREFERENCE, Z09_NULL_MX_FOUND_WITH_OTHER_MX.

@matsduf

matsduf commented Jul 6, 2020

Copy link
Copy Markdown
Contributor Author

Should Z09_ARPA_MAIL_DOMAIN_NOT_REQUIRED and Z09_TLD_MAIL_DOMAIN_NOT_REQUIRED be INFO or WARNING ?

INFO. They are outputted if an ARPA domain or TLD, respectively, has no MX or an Null MX, which should be considered to be normal.

Maybe tests should be added to report Z09_NULL_MX_FOUND_WITH_NON_ZERO_PREFERENCE, Z09_NULL_MX_FOUND_WITH_OTHER_MX.

Good proposal. I will add that.

@cgsecurity

Copy link
Copy Markdown

Should a warning be emitted if an arpa domain or TLD has an MX (except NULL_MX) ?

In my opinion, Z09_NULL_MX_WITH_NON_ZERO_PREFERENCE and Z09_NULL_MX_WITH_OTHER_MX should be WARNING
"To indicate that a domain does not accept email, it advertises a
single MX RR (see Section 3.3.9 of [RFC1035]) with an RDATA section
consisting of preference number 0 and a zero-length label, written in
master files as ".", as the exchange domain, to denote that there
exists no mail exchanger for a domain."

@matsduf

matsduf commented Jul 6, 2020

Copy link
Copy Markdown
Contributor Author

Should a warning be emitted if an arpa domain or TLD has an MX (except NULL_MX) ?

I think a WARNING or even NOTICE would definitely be too strong. I cannot see that an MX there would create a problem. See Severity Level Definitions. I noticed that .ax has an MX.

According to RFC 5321 a TLD can be used as mail domain, and then it should be OK to have MX.

In my opinion, Z09_NULL_MX_WITH_NON_ZERO_PREFERENCE and Z09_NULL_MX_WITH_OTHER_MX should be WARNING
"To indicate that a domain does not accept email, it advertises a
single MX RR (see Section 3.3.9 of [RFC1035]) with an RDATA section
consisting of preference number 0 and a zero-length label, written in
master files as ".", as the exchange domain, to denote that there
exists no mail exchanger for a domain."

I cannot see that non-zero preference could create such a problem. A second MX could possibly fool a non-compliant SMTP client (i.e. a client that does not understand "Null MX") into sending the mail to the secondary MX. I will raise the second to WARNING.

@matsduf

matsduf commented Jul 7, 2020

Copy link
Copy Markdown
Contributor Author

I found, or was sent, a reference on using dotless domains as mail domains, "Dotless Domains Considered Harmful". I will update the specification with a message on level WARNING if a TLD has an non-Null MX.

@matsduf matsduf force-pushed the update-zone09 branch 2 times, most recently from 1d5024f to d4532a1 Compare July 8, 2020 09:02
sandoche2k
sandoche2k previously approved these changes Jul 17, 2020
@matsduf

matsduf commented Jul 17, 2020

Copy link
Copy Markdown
Contributor Author

@vlevigneron, any comment on this PR before I merge?

@mattias-p mattias-p left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This rewrite is quite an expansion! All in all it looks very good. I have a few suggestions.

Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
@matsduf matsduf modified the milestones: v2020.1, v2020.2 Sep 14, 2020
@matsduf matsduf modified the milestones: v2020.2, v2021.1 Mar 15, 2021
@matsduf matsduf modified the milestones: v2021.1, v2021.2 May 27, 2021
@matsduf matsduf force-pushed the update-zone09 branch 3 times, most recently from 0f64ef2 to 2eab47d Compare July 28, 2021 13:45

@ghost ghost left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just few typos, suggestions and a question.

Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md
matsduf added 10 commits July 15, 2022 16:20
* Adapts to draft template (zonemaster#971)
* Messages are updated.
* Informational messages removed to keep down the amount of messages.
* Adds reference to "Query and responds defaults".
* Updates the message tags to make them shorter.
* Updates the message tag table to make it follow proposed
  updates to the specification template.
  * Adds message ID
  * Adds arguments to message ID
* Editorial updates.
@matsduf matsduf requested review from tgreenx and removed request for sandoche2k and vlevigneron July 15, 2022 14:26
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
Comment thread docs/specifications/tests/Zone-TP/zone09.md
@matsduf matsduf requested a review from a user July 19, 2022 14:42
@matsduf

matsduf commented Jul 20, 2022

Copy link
Copy Markdown
Contributor Author

@PNAX, please re-review.

ghost
ghost previously approved these changes Jul 20, 2022

@ghost ghost left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one last comment, otherwise this is good to me

Comment thread docs/specifications/tests/Zone-TP/zone09.md Outdated
@matsduf matsduf dismissed ghost ’s stale review via 155f654 July 20, 2022 11:38
1. *Child Zone* is the root zone ("."), or
1. *Child Zone* is a [TLD], or
2. *Child Zone* is a zone in the .ARPA tree.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I realize we are not outputting the list of found MX records at the end of this test anymore. This would be nice to list all found MX as NOTICE as before. This can be of value to know how the domain is configured to handle mails.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-TestCase Area: Test case specification or implementation of test case

Projects

None yet

Development

Successfully merging this pull request may close these issues.

zone09 check for .in-addr.arpa and .ip6.arpa

5 participants