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.

Sign up for GitHub

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

Jump to bottom

DNAME not applied more than once to resolve the query #151

Closed
SivaKesava1 opened this issue Jan 10, 2021 · 2 comments
Closed

DNAME not applied more than once to resolve the query #151

SivaKesava1 opened this issue Jan 10, 2021 · 2 comments

Comments

@SivaKesava1
Copy link

Same issue as in Knot: https://gitlab.nic.cz/knot/knot-dns/-/issues/714
@wcawijngaards
Copy link
Member

It is a feature, not a bug. The reason is that it is seen as a DNAME loop, because the same DNAME is applied twice. If it was two different DNAMEs then there would be two DNAMEs in the answer.

@wcawijngaards
Copy link
Member

But fixed it anyway, because the same behaviour as BIND is desirable. The fix tests if the CNAME can be added. That results in the NS record returned in the example you gave. Thanks for the report!

wcawijngaards added a commit that referenced this issue Jan 11, 2021
@wcawijngaards
- For #151: fix to not produce loops in output.
356c2b5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@wcawijngaards @SivaKesava1