Skip to content
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

Missing message tag when running Consistency06 on non-responding name servers #1300

Open
matsduf opened this issue Nov 9, 2023 · 0 comments
Labels
T-Bug Type: Bug in software or error in test case description

Comments

@matsduf
Copy link
Contributor

matsduf commented Nov 9, 2023

Using the test zones specified in zonemaster/zonemaster#1213 we have some test zones (scenarios) where NO_RESPONSE. For some of the test zones (scenarios) the tag is outputted, for others it is not. E.g. for test zone no-response.consistency06.xa none of the name server IP addresses are responding (on purpose) but the tag is not outputted.

After some investigation I have come to the following conclusion:

For a non-responding name server to be listed in NO_RESPONSE at lease one of the following requirements must be fullfilled:

  • The zone must be available and the name serverin question must be listed in that zone as an NS.
  • The name server in question must be included in the call as "fake delegation".

In case of no-response.consistency06.xa, the zone is not available since none of the name servers for it responds. By inspecting output from tcpdump I can see that queries are sent to the non-responding name server IPs.

First running the test of the zone using the delegated path from the private root:

$ zonemaster-cli no-response.consistency06.xa --raw  --test Consistency/consistency05 --hints COMMON/hintfile --level debug | grep -vE 'EXTERNAL_QUERY|IS_BLACKLISTED|LOOKUP_ERROR|DEPENDENCY_VERSION'
   0.00 DEBUG    START_TIME   string=2023-11-13 12:30:28 +0000; time_t=1699878628
   0.00 DEBUG    TEST_ARGS   args=Zonemaster::Engine::Zone=HASH(0x55f417e47688); module=consistency; testcase=consistency05
   0.00 INFO     GLOBAL_VERSION   version=v4.7.3
   0.00 DEBUG    MODULE_VERSION   module=Zonemaster::Engine::Test::Consistency; version=v1.1.16
   0.00 DEBUG    TEST_CASE_START   testcase=consistency05
  40.26 ERROR    CHILD_ZONE_LAME   
  40.26 DEBUG    TEST_CASE_END   testcase=consistency05
  40.26 DEBUG    MODULE_END   module=Consistency

A second run with "fake delegation" added. Note that NO_RESPONSE now appear.

$ zonemaster-cli no-response.consistency06.xa --raw  --test Consistency/consistency05 --hints COMMON/hintfile --ns ns1.no-response.consistency06.xa/127.14.6.31 --ns ns2.no-response.consistency06.xa/127.14.6.32  --level debug | grep -vE 'EXTERNAL_QUERY|IS_BLACKLISTED|LOOKUP_ERROR|DEPENDENCY_VERSION|ADDED_FAKE_DELEGATION'
   0.00 DEBUG    START_TIME   string=2023-11-13 12:27:52 +0000; time_t=1699878472
   0.00 DEBUG    TEST_ARGS   args=Zonemaster::Engine::Zone=HASH(0x558fdb436290); module=consistency; testcase=consistency05
   0.00 INFO     GLOBAL_VERSION   version=v4.7.3
   0.00 DEBUG    MODULE_VERSION   module=Zonemaster::Engine::Test::Consistency; version=v1.1.16
   0.00 DEBUG    TEST_CASE_START   testcase=consistency05
   0.08 DEBUG    NO_RESPONSE   ns=ns1.no-response.consistency06.xa/127.14.6.31
   0.08 DEBUG    NO_RESPONSE   ns=ns1.no-response.consistency06.xa/127.14.6.31
   0.08 DEBUG    NO_RESPONSE   ns=ns2.no-response.consistency06.xa/127.14.6.32
   0.08 DEBUG    NO_RESPONSE   ns=ns2.no-response.consistency06.xa/127.14.6.32
   0.08 ERROR    CHILD_ZONE_LAME   
   0.08 DEBUG    TEST_CASE_END   testcase=consistency05
   0.08 DEBUG    MODULE_END   module=Consistency
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-Bug Type: Bug in software or error in test case description
Projects
None yet
Development

No branches or pull requests

1 participant