Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
I just migrated our dns configuration from 6 to 8. Our dynamic dns updates from Windows machines stopped working. We use KRB5 keytab, gss updates. After some investigation I found that after commenting all "deny subdomain lines it started to work again".
This is working:
update-policy {
grant ad1$@MY.DOMAIN subdomain my.domain. ANY;
grant ad2$@MY.DOMAIN subdomain my.domain. ANY;
grant dc1$@MY.DOMAIN subdomain my.domain. ANY;
grant dc2$@MY.DOMAIN subdomain my.domain. ANY;
deny * name ad1.my.domain. ANY;
deny * name ad2.my.domain. ANY;
deny * name dc1.my.domain. ANY;
deny * name dc2.my.domain. ANY;
grant MY.DOMAIN ms-self . A AAAA;
};
It logs "view internal: update 'my.domain/IN' denied" but updates works well.
BUT with this ms-self clause IS NOT working:
update-policy {
grant ad1$@MY.DOMAIN subdomain my.domain. ANY;
grant ad2$@MY.DOMAIN subdomain my.domain. ANY;
grant dc1$@MY.DOMAIN subdomain my.domain. ANY;
grant dc2$@MY.DOMAIN subdomain my.domain. ANY;
deny * name ad1.my.domain. ANY;
deny * name ad2.my.domain. ANY;
deny * name dc1.my.domain. ANY;
deny * name dc2.my.domain. ANY;
deny * subdomain anything.really.does.not.matter.what. ANY;
grant MY.DOMAIN ms-self . A AAAA;
};
Bind is logging "update failed: rejected by secure update (REFUSED)".
It really does not matter what subdomain I put into subdomain line, every subdomain option breaks policies following that line. Btw. it was working fine in major version 6.
Bind version: BIND 9.11.4-P2-RedHat-9.11.4-17.P2.el8_0.1
I have tried reproducing it on freeipa instance, but could not reproduce this issue.
BIND update policy: deny * subdomain anything.really.does.not.matter.what. ANY; grant IPA.TEST krb5-self * A; grant IPA.TEST krb5-self * AAAA; grant IPA.TEST krb5-self *
SSHFP;
With this, update worked just fine. If it is ms kerberos specific problem, it would take more time to validate.
Comment 6RHEL Program Management
2021-07-05 07:30:04 UTC
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.
I just migrated our dns configuration from 6 to 8. Our dynamic dns updates from Windows machines stopped working. We use KRB5 keytab, gss updates. After some investigation I found that after commenting all "deny subdomain lines it started to work again". This is working: update-policy { grant ad1$@MY.DOMAIN subdomain my.domain. ANY; grant ad2$@MY.DOMAIN subdomain my.domain. ANY; grant dc1$@MY.DOMAIN subdomain my.domain. ANY; grant dc2$@MY.DOMAIN subdomain my.domain. ANY; deny * name ad1.my.domain. ANY; deny * name ad2.my.domain. ANY; deny * name dc1.my.domain. ANY; deny * name dc2.my.domain. ANY; grant MY.DOMAIN ms-self . A AAAA; }; It logs "view internal: update 'my.domain/IN' denied" but updates works well. BUT with this ms-self clause IS NOT working: update-policy { grant ad1$@MY.DOMAIN subdomain my.domain. ANY; grant ad2$@MY.DOMAIN subdomain my.domain. ANY; grant dc1$@MY.DOMAIN subdomain my.domain. ANY; grant dc2$@MY.DOMAIN subdomain my.domain. ANY; deny * name ad1.my.domain. ANY; deny * name ad2.my.domain. ANY; deny * name dc1.my.domain. ANY; deny * name dc2.my.domain. ANY; deny * subdomain anything.really.does.not.matter.what. ANY; grant MY.DOMAIN ms-self . A AAAA; }; Bind is logging "update failed: rejected by secure update (REFUSED)". It really does not matter what subdomain I put into subdomain line, every subdomain option breaks policies following that line. Btw. it was working fine in major version 6. Bind version: BIND 9.11.4-P2-RedHat-9.11.4-17.P2.el8_0.1