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

add_fake_delegation() does not respect changed root #1344

Open
matsduf opened this issue May 8, 2024 · 2 comments
Open

add_fake_delegation() does not respect changed root #1344

matsduf opened this issue May 8, 2024 · 2 comments
Assignees
Labels
P-High Priority: Issue to be solved before other T-Bug Type: Bug in software or error in test case description
Milestone

Comments

@matsduf
Copy link
Contributor

matsduf commented May 8, 2024

When root has been change all lookups should respect that changed root. add_fake_delegation() does not.

With root given for the following command ns3-undelegated-child.basic01.xa can be resolved, but nsa.dnsnode.net cannot. Using public root, the reverse is true. FAKE_DELEGATION_NO_IP is not expected for ns3-undelegated-child.basic01.xa.

$ zonemaster-cli --raw  --show-testcase --test basic01 --hints COMMON/hintfile  --ns ns3-undelegated-child.basic01.xa --ns nsa.dnsnode.net child.parent.good-undel-1.basic01.xa
   0.40 ERROR    Unspecified    FAKE_DELEGATION_NO_IP  domain=child.parent.good-undel-1.basic01.xa; nsname=ns3-undelegated-child.basic01.xa

This might prevent testing of scenarios with undelegated zones.

@matsduf matsduf added the T-Bug Type: Bug in software or error in test case description label May 8, 2024
@matsduf matsduf added this to the v2024.1 milestone May 8, 2024
@tgreenx
Copy link
Contributor

tgreenx commented May 15, 2024

Indeed, this is a bug due to the fact that out of bailiwick lookups for fake delegations are being done in Zonemaster-LDNS rather than Engine, when $fill_in_empty_oob_glue = 1:

https://github.com/zonemaster/zonemaster-engine/blob/v5.0.0/lib/Zonemaster/Engine.pm#L142

@matsduf matsduf modified the milestones: v2024.1, v2024.2 Jul 3, 2024
@matsduf matsduf added the P-High Priority: Issue to be solved before other label Jul 10, 2024
@matsduf
Copy link
Contributor Author

matsduf commented Sep 13, 2024

@tgreenx, is this something you could look at? It limits the possibilities in test scenarios.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P-High Priority: Issue to be solved before other T-Bug Type: Bug in software or error in test case description
Projects
None yet
Development

No branches or pull requests

2 participants