On Thu, 2016-06-23 at 17:24 +0200, Timotheus Pokorra wrote:
Hello Martin,
Hostname 'ds389.limbo.local' is valid, but none of the IP addresses resolve back to ds389.limbo.local
- address 10.30.33.10 resolves to host ds389.jalacloud.local
Error: Could not create directory server instance 'ds389'. Exiting . . . Log file is '/tmp/setupyR6ywt.log'
where ds389 is the hostname, and limbo.local the domain
Try to add to your /etc/hosts file: 10.30.33.10 ds389.limbo.local ds389.jalacloud.local
I think the keyword to search for on the internet is: fully qualified domain name
To expand on this, you are likely missing, or have misconfigured the following dns record:
I0> host 10.30.33.10 Host 10.33.30.10.in-addr.arpa. not found: 3(NXDOMAIN)
You can add 10.33.30.10.in-addr.arpa to your reverse DNS zone if avaliable. Something like:
$ORIGIN 33.30.10.in-addr.arpa 10 IN PTR ds389.limbo.local
OR you can change your DS setup to use ds389.jalacloud.local.
By editing the hosts file, you may now have a scenario where:
* To the ldap server 10.33.30.10.in-addr.arpa. is now ds389.limbo.local via localhost in the hosts file * To all other systems 10.33.30.10.in-addr.arpa is ds389.jalacloud.local from DNS.
Saying this, to LDAP the proper function of the reverse DNS is not very important.