Red Hat Bugzilla – Bug 878485
ipa trust-add prints misleading information about required DNS setting
Last modified: 2013-02-21 04:30:33 EST
This bug is created as a clone of upstream ticket: https://fedorahosted.org/freeipa/ticket/3261 `ipa trust-add` command recommends DNS forwarder set-up but it should recommend normal DNS delegation in first place. Forwarders should be option of last resort. Current output: {{{ [root@cypher ~]# ipa trust-add --type=ad adlab.qe --admin Administrator --password Active directory domain administrator's password: ipa: ERROR: Unable to resolve domain controller for 'adlab.qe' domain. Additional instructions: IPA manages DNS, please configure forwarder to 'adlab.qe' domain using following CLI command. Make sure to replace DNS_SERVER and IP_ADDRESS by actual values corresponding to the trusted domain's DNS server: ipa dnszone-add adlab.qe --name-server=[DNS_SERVER] --admin-email='hostmaster@adlab.qe' --force --forwarder=[IP_ADDRESS] --forward-policy=only When using Web UI, please create DNS zone for domain 'adlab.qe' first and then set forwarder and forward policy. }}} It should say somenthing like: {{{ IPA manages DNS, please create delegation records (NS + A or AAAA records) for AD managed DNS domains. NS record for name 'adlab' in zone 'qe' should countain *name* of AD name server. A or AAAA glue records for AD name server have to be created to ensure proper name server resolution. If you set global forwarders (in named.conf or in LDAP) to value different from your AD server then you should specify forward policy to 'none' for zone 'qe.'. Implicit policy 'first' will send all queries to global forwarders and NS records will be ineffective. You can set DNS forwarding up if you can't create delegation records for some reason. ... original text follows ... }}}
Fixed upstream. master: a9bac3d600bc8eb9699e146b1132f712cccabdfd ipa-3-0: 6e26bf31fed7321baca58a87691ab3310afc9840
[root@wazwan ~]# ipa dnszone-find Zone name: 201.65.10.in-addr.arpa. Authoritative nameserver: wazwan.ipalab.qe. Administrator e-mail address: hostmaster.ipalab.qe. SOA serial: 1359655483 SOA refresh: 3600 SOA retry: 900 SOA expire: 1209600 SOA minimum: 3600 Active zone: TRUE Allow query: any; Allow transfer: none; Zone name: ipalab.qe Authoritative nameserver: wazwan.ipalab.qe. Administrator e-mail address: hostmaster.ipalab.qe. SOA serial: 1359655517 SOA refresh: 3600 SOA retry: 900 SOA expire: 1209600 SOA minimum: 3600 Active zone: TRUE Allow query: any; Allow transfer: none; ---------------------------- Number of entries returned 2 ---------------------------- [root@wazwan ~]# ipa trust-add --type=ad adlab.qe --admin Administrator --password Active directory domain administrator's password: ipa: ERROR: Unable to resolve domain controller for 'adlab.qe' domain. Additional instructions: IPA manages DNS, please verify your DNS configuration and make sure that service records of the 'adlab.qe' domain can be resolved. Examples how to configure DNS with CLI commands or the Web UI can be found in the documentation. Conversation to clarify difference in description and result <steeve> sbose: https://bugzilla.redhat.com/show_bug.cgi?id=878485 <steeve> sbose: Is this expected http://pastebin.test.redhat.com/125629 for the above bug? <sbose> steeve, I think so, anything wrong with it? * enewland has quit (Quit: Leaving) * enewland (~enewland@dhcp-187-220.bos.redhat.com) has joined #ipa <ab> steeve: there was discussion on ipa team list to remove configuration description in favor of documentation <steeve> sbose: no. It was different from the description <ab> steeve: since there are quite few variations <ab> so I would say what you see in pastebin is correct and what is expected. <steeve> sbose: ab ok.. Thanks! * arubin (~arubin@dhcp-185-224.bos.redhat.com) has joined #ipa <sbose> steeve, ah, ok, we agreed to not give any specific suggestion because other solution might be better in specific environments. <steeve> sbose: yes.. makes sense
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0528.html