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

Updates data file for unit test #1

Open
wants to merge 2 commits into
base: cname-in-recursor
Choose a base branch
from

Conversation

matsduf
Copy link

@matsduf matsduf commented Nov 29, 2023

Now LOOPED-CNAME-IN-ZONE-2 passes.

tgreenx and others added 2 commits November 28, 2023 12:20
This commit makes Engine able to follow CNAMEs when doing recursive lookups.
Currently CNAMEs will be followed when all of the following are true:
	- the response has RCODE "NoError"
	- the answer section of the response does not contain records of the queried type, but does contain at least one CNAME record for the query name
	- the answer section of the response does not contain multiple CNAME records with the same owner name
	- the final target of the CNAME record(s) chain has not been followed before
	- there are no records of the queried type with owner name as the final target of the CNAME record(s)

Three system, debug level messages are created: 'CNAME_LOOP_INNER', 'CNAME_LOOP_OUTER' and 'CNAME_MULTIPLE_FOR_NAME'.

Some test cases have been modified to account for this new behavior. Unitary tests have also been updated.
@tgreenx tgreenx force-pushed the cname-in-recursor branch 2 times, most recently from 1324029 to 32244e9 Compare December 7, 2023 12:53
@tgreenx tgreenx force-pushed the cname-in-recursor branch from 5756f49 to 2cff836 Compare May 14, 2024 15:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants