Hi Rob,

Thank you for the reply,

Here below the output of dig command, it looks like is returing the right hostname of ipa server in SECTION SERVER:

#dig -x 172.16.x.y

; <<>> DiG 9.9.4-RedHat-9.9.4-74.el7_6.1 <<>> -x 172.16.x.y
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54279
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 2

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;y.x.16.172.in-addr.arpa.     IN      PTR

;; ANSWER SECTION:
y.x.16.172.in-addr.arpa. 86400 IN     PTR     ipa.server.example.com.x.16.172.in-addr.arpa.
;; ADDITIONAL SECTION:
ipa.server.example.com. 1200 IN     A       172.16.x.y

;; Query time: 0 msec
;; SERVER: 172.16.x.y#53(172.16.x.y)
;; WHEN: Thu Aug 01 10:12:57 EDT 2019
;; MSG SIZE  rcvd: 151

On Wed, Jul 31, 2019 at 5:40 PM Rob Crittenden <rcritten@redhat.com> wrote:

Boudjoudad Abdelkader via FreeIPA-users wrote:
> Hi,
> I'm trying to install an IPA server replica from but i have  the issue
> below, i did:
> - Remove the IP of ipa server master from /etc/hosts
> - Check if there is a problem with ipa-client-install (working fine) 
> - dig IP-ipa-server (resolved)
> Non of these steps works!
>
> I did some researches and it looks like this is a bug, is there a
> workaround ?
>
> ERROR:
> WARNING: conflicting time&date synchronization service 'chronyd' will be
> disabled in favor of ntpd
>
> Your system may be partly configured.
> Run /usr/sbin/ipa-server-install --uninstall to clean up.
>
> ipapython.admintool: ERROR  The host name freeipa-replica.example.com
> <http://freeipa-replica.example.com> does not match the primary host
> name freeipa-replica.example.com.x.yy.zzz.in-addr.arpa. Please check
> /etc/hosts or DNS name resolution
> ipapython.admintool: ERROR    The ipa-replica-install command failed.
> See /var/log/ipareplica-install.log for more information

Something is definitely broken in your DNS. Your forward lookup is
apparently returning a reverse-like answer.
freeipa-replica.example.com.x.yy.zzz.in-addr.arpa is in a reverse zone.

dig -x <your ip>

is a proper reverse query. The answer should be something like:

12.122.168.192.in-addr.arpa. 86400 IN      PTR     ipa.example.test.

rob