mirror of
https://salsa.debian.org/freeipa-team/freeipa.git
synced 2024-12-23 15:40:01 -06:00
36b975804f
In scenario: 1. make sure that reverse zone doesn't have the desired PTR record 2. open host page of the host with matchnig the A record, e.g.: https://server.pvoborni.test/ipa/ui/#/e/host/details/test2.pvoborni.test 3. click on the "Host name" link, it will bring us to it's DNS record page. E.g., https://server.pvoborni.test/ipa/ui/#/e/dnsrecord/details/pvoborni.test&test2 ! notice the missing '.' in the URL after zone name (pvoborni.test) 4. click on the A record , dialog will show up, saying "record not found" 5. click on the "create DNS record" PTR record created by Web UI doesn't have trailing '.' (is not fully qualified record) even if the DNS zone is. This patch is fixing the link to the DNS Record page so that the page then correctly gets the DNS Zone name and thus creates a correct fully qualified PTR record. https://bugzilla.redhat.com/show_bug.cgi?id=2009114 https://pagure.io/freeipa/issue/9036 Signed-off-by: Petr Vobornik <pvoborni@redhat.com> Reviewed-By: Florence Blanc-Renaud <flo@redhat.com> |
||
---|---|---|
.. | ||
certmonger | ||
custodia | ||
html | ||
migration | ||
oddjob | ||
restart_scripts | ||
share | ||
tools | ||
ui | ||
updates | ||
wsgi | ||
Makefile.am | ||
README.schema |
Ground rules on adding new schema Brand new schema, particularly when written specifically for IPA, should be added in share/*.ldif. Any new files need to be explicitly loaded in ipaserver/install/dsinstance.py. These simply get copied directly into the new instance schema directory. Existing schema (e.g. in an LDAP draft) may either be added as a separate ldif in share or as an update in the updates directory. The advantage of adding the schema as an update is if 389-ds ever adds the schema then the installation won't fail due to existing schema failing to load during bootstrap. If the new schema requires a new container then this should be added to install/bootstrap-template.ldif.