Created attachment 489445 [details]
part of ipaserver-install log
Description of problem:
When server is installed using --no-reverse option, reverse zone is set up.
install ipa sersever using cmd:
ipa-server-install --setup-dns --no-forwarders --no-reverse
Zone name: 19.16.10.in-addr.arpa.
Authoritative nameserver: rhel61-server2.testrelm.
Administrator e-mail address: root.19.16.10.in-addr.arpa.
Install logs indicate - "setting up reverse zone" step is taken.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.ipa-server-install --setup-dns --no-forwarders --no-reverse
includes: Zone name: 19.16.10.in-addr.arpa.
Should not set up reverse zone.
Not seeing this issue any more when using ipa-server-2.0.0-22.el6.x86_64. Did this get addressed?
No, it isn't fixed upstream yet either. Note that this only happened in interactive mode.
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
Cause: When setting up DNS a reverse zone was always created regardless of the --no-reverse option when installing in interactive mode.
Consequence: A zone was being created that the user did not want.
Fix: Create a reverse zone only if either it was asked for interactively or on the command-line.
Result: The reverse DNS zone is not created when the user specifies either --no-reverse or answers no in the interactive installer.
Verified using ipa-server-2.1.3-8.el6.x86_64
# ipa-server-install --setup-dns --no-forwarders --no-reverse
# ipa dnszone-find
Zone name: testrelm
Authoritative nameserver: ipa-replica.testrelm.
Administrator e-mail address: root.ipa-replica.testrelm.
SOA serial: 2011041101
SOA refresh: 3600
SOA retry: 900
SOA expire: 1209600
SOA minimum: 3600
Active zone: TRUE
Number of entries returned 1
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.