RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 960777 - 'ipa dnszone-add' should prompt for nameserver IP address if there is no existing A/AAAA record
Summary: 'ipa dnszone-add' should prompt for nameserver IP address if there is no exis...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: ipa
Version: 7.0
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: Namita Soman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-07 23:43 UTC by Dmitri Pal
Modified: 2015-01-21 15:39 UTC (History)
3 users (show)

Fixed In Version: ipa-3.2.1-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-06-13 11:30:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Dmitri Pal 2013-05-07 23:43:48 UTC
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/3603

When using 'ipa dnszone-add' do add a new zone it prompts only for:
- Authoritative nameserver:
- Zone name:
- Administrator e-mail address [...]:
and fails with the following error:
"ipa: ERROR: Nameserver '...' does not have a corresponding A/AAAA record"

When you try to add A/AAAA record for the Nameserver you'll end up with:
"ipa: ERROR: example: DNS zone not found"

So you end up in a situation where you can not add new zone because you don't
have A/AAAA record for the Nameserver AND can not add new A/AAAA record for the
Nameserver because you have no zone.

Comment 4 Dmitri Pal 2013-08-29 16:17:16 UTC
Linked to https://fedorahosted.org/freeipa/ticket/3320

Comment 5 Michael Gregg 2014-01-03 22:04:13 UTC
Verified that dnszone asks for IP address in it needs to.

Verified against ipa-server-3.3.3-6.el7.x86_64

[root@ipaqavmb ~]# ipa dnszone-add 
Authoritative nameserver: newhostserver.newzone.com.
Zone name: newzone.com
Administrator e-mail address [hostmaster.newzone.com.]: 
Nameserver IP address: 10.16.98.180
  Zone name: newzone.com
  Authoritative nameserver: newhostserver.newzone.com.
  Administrator e-mail address: hostmaster.newzone.com.
  SOA serial: 1388786556
  SOA refresh: 3600
  SOA retry: 900
  SOA expire: 1209600
  SOA minimum: 3600
  BIND update policy: grant TESTRELM.COM krb5-self * A; grant TESTRELM.COM krb5-self * AAAA; grant TESTRELM.COM krb5-self * SSHFP;
  Active zone: TRUE
  Dynamic update: FALSE
  Allow query: any;
  Allow transfer: none;

Comment 6 Ludek Smid 2014-06-13 11:30:38 UTC
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.


Note You need to log in before you can comment on or make changes to this bug.