As a FreeIPA server admin, I want to understand why a hostname record in the DNS zone disappear so that I could do something to fix the problem.
In a FreeIPA production environment, under Centos 7, with 30 client hosts and 2 servers (one replica) I have one DNS zone to manage. A trust with an AD is set with an other domain.
All is working very well with policies and all that.
All my IPA clients are setup with Puppet which means that every piece of my LAN is configured exactly the same. And all my clients are all Debian Buster provisioned with the same Preseed.
Every client installs with this parameter set :
/usr/sbin/ipa-client-install \ --domain=${domain} \ --realm=${realm} \ --principal='${principal}' \ --password='${password}' \ --mkhomedir \ --force-join \ --no-dns-sshfp \ --enable-dns-updates \ --unattended
But one of my clients lost its record in the IPA DNS zone. No more hostname or IP present after few hours or few days.
Well I can't say! It affects only one host from a set of 30...
DNS record for the host disappear
DNS record stays in place
le paquet freeipa-server n'est pas installé le paquet freeipa-client n'est pas installé ipa-server-4.6.5-11.el7.centos.3.x86_64 ipa-client-4.6.5-11.el7.centos.3.x86_64 389-ds-base-1.3.9.1-12.el7_7.x86_64 pki-ca-10.5.16-5.el7_7.noarch krb5-server-1.15.1-37.el7_7.2.x86_64
Every time I add this host entry it disappear within one day...
Could you provide help how to get log or information about this... Which services are involved in removing DNS entry?
Thanks
Well, after digging I finally got the good behavior!
For your interest I discovered here https://bugzilla.redhat.com/show_bug.cgi?id=1077464 the parameter dyndns_iface with hardcoded the name of the network interface used when enrolling to IPA.
But now that I created a bridge, br0, with my network interface as a salve to it...it breaks the update.
That's why dyndns update failed and so removed my records in the IPA DNS.
After I changed dyndns_iface value to my bridge interface br0 the DNS stopped to remove my entry...great!
Conclusion: manually set the dyndns_iface value when you use a bridge.
Sorry for the false issue, I hope it will be helpful for someone one day (nobody is using bridge?)
All the best
Metadata Update from @slamy: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.