problem running setup ds admin "Error: Could not create directory server instance"

Hi, I am trying to deploy  389ds but I have an error running setup-ds-admin, after select the typical setup and provide the required data, the isntaller ends with the following error: 
The interactive phase is complete.  The script will now set up your
servers.  Enter No or go Back if you want to change something.

Are you ready to set up your servers? [yes]: y
Creating directory server . . .
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
I googled for any references without luck, the only  references was 6 ago, I tried in a fresh installed centos 7.1 server, any clue about this?

[Timotheus Pokorra]

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

hope this helps,
  Timotheus

Thanks a lot, apparently that work, weird since apparently the fqdn was working well in the dns

[William Brown]

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.