When creating a server instance, DSUtil::checkHostname checks that the FQDN can be strictly resolved.
It is necessary for the Admin Server installation via setup-ds-admin.pl, but there could be a case the constraint is not necessary. That said, it should be useful to add an option to relax the constraint.
attachment 0001-Ticket-48332-allow-users-to-specify-to-relax-the-FQD.patch
commit c919cec1403729dc700492df3c9d2a93d735ae64 To ssh://git.fedorahosted.org/git/389/ds.git 8c17df6..026956c master -> master
Thank you!
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1292649
Backported to 1.3.4, 1.3.3, and 1.2.11:
Pushed to 389-ds-base-1.3.4: b91aad0..5d0f573 389-ds-base-1.3.4 -> 389-ds-base-1.3.4 commit 5d0f57335c1bf97529849d5d47cad769083052d0
Pushed to 389-ds-base-1.3.3: 44acc45..e62ef7f 389-ds-base-1.3.3 -> 389-ds-base-1.3.3 commit e62ef7f4d19d78d015efa915f7740f4d8b615da4
Pushed to 389-ds-base-1.2.11: 8265138..3f2ea36 389-ds-base-1.2.11 -> 389-ds-base-1.2.11 commit 3f2ea36e763c8e08b88265bd365c6daa5081419c
Metadata Update from @firstyear: - Issue assigned to firstyear - Issue set to the milestone: 1.2.11.33
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1663
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)