-
Notifications
You must be signed in to change notification settings - Fork 903
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
DNAME occlusion #1361
Comments
I am just hit by this bug. Any chance this gets fixed some time? Also the description of "dname-processing" confuses me: |
As it only occurs when there is garbage in the database, it does not have a super high priority.
The 'Do not combine with DNSSEC' remark surprises me!
Those are the same thing. DNAME processing -is- CNAME synthesis. |
In my tests with Auth 4.1.5 DNAME does not work without dname-processing=yes. Hence, the name of the option is correct, the description make me thing this is only needed for CNAME synthesis but it is needed always for DNAME to work - even without subordinate labels. |
Again, those are the same thing. I'm confused - it looks like you are saying 'in 4.1.5, DNAME works, except it does not generate CNAMEs'. In that case, what part of DNAME is working? |
Sorry for the confusion. Indeed there 3 issues:
|
From
regression-tests/zones/test.com
:When queried for a.d, we return the A, while we should be synthesising a CNAME.
Tasks:
The text was updated successfully, but these errors were encountered: