Hide Forgot
When user installs a new DNS instance on a replica, no new NS records are added to the zone. Admin must do so manually. It would be nice to have this documented for 2.0 https://fedorahosted.org/freeipa/ticket/1034 Jakub, please add more details to this BZ.
We discussed this issue yesterday with Simo and agreed that we probably can't fix it for 2.0 GA, so we should at least document this for the time being and fix later - so please bear in mind that we're describing a faulty behaviour that would change in a future version. When a replica is installed, it doesn't contain a DNS server by default even if the master does. Admin must install the DNS instance manually with ipa-dns-install. The problem is, that the current code wouldn't add a NS record for this new name server into any of the managed DNS zones. The admin must add them manually using "ipa dnsrecord-add <zone> @ --ns-rec <replica-with-DNS-FQDN>". As with ordinary NS records, the FQDN must really be fully qualified (=end with a dot, for example ns.example.com.) otherwise Bind would treat the hostname as relative to the domain.
Added section 7.4.2. Installing and Configuring DNS on IPA Replicas Setting MODIFIED. Will brew and push later this week. Created commit 3efa563
Latest build now available on http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/96/html/Enterprise_Identity_Management_Guide/index.html Current version: Red_Hat_Enterprise_Linux-Enterprise_Identity_Management_Guide-96-web-en-US-0.6-25.el5
(In reply to comment #3) > Latest build now available on > http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/96/html/Enterprise_Identity_Management_Guide/index.html > > Current version: > Red_Hat_Enterprise_Linux-Enterprise_Identity_Management_Guide-96-web-en-US-0.6-25.el5 Looks good to me, thank you.