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 856293 - Nameserver does not have a corresponding A/AAAA record while creating new dns zone
Summary: Nameserver does not have a corresponding A/AAAA record while creating new dns...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa
Version: 6.4
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: 2012-09-11 16:39 UTC by Dmitri Pal
Modified: 2013-02-21 09:19 UTC (History)
6 users (show)

Fixed In Version: ipa-3.0.0-10.el6
Doc Type: Known Issue
Doc Text:
When attempting to create a new DNS zone, ipa can report that the name server does not have an A/AAAA record even when it does.
Clone Of:
Environment:
Last Closed: 2013-02-21 09:19:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0528 0 normal SHIPPED_LIVE Low: ipa security, bug fix and enhancement update 2013-02-21 08:22:21 UTC

Description Dmitri Pal 2012-09-11 16:39:10 UTC 
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/3063

[[br]]Description of problem:
[[br]]When attempting to create a new dns zone, ipa reports the name server does not have a A record when it does.

[[br]]Version-Release number of selected component (if applicable):
[[br]]freeipa-server-2.99.0-0.20120829T2002Zgit7e9eb9c.fc17.x86_64
[[br]]bind-dyndb-ldap-1.1.0-0.20120828T1109Zgit6114ae2.fc17.x86_64

[[br]]How reproducible:
[[br]]Always

[[br]]Steps to Reproduce:
[[br]]1. install ipa with dns support
[[br]]2. ipa dnszone-add --name-server=<fqdn of master> --admin-email=ipaqar.redhat.com --serial=2010010701 --refresh=303 --retry=101 --expire=1202 --minimum=33 --ttl=55 idnszone.com

 
[[br]]Actual results:
[root@zippyvm2 ipa-dns]# ipa dnszone-add --name-server=zippyvm2.testrelm.com --admin-email=ipaqar.redhat.com --serial=2010010701 --refresh=303 --retry=101 --expire=1202 --minimum=33 --ttl=55 idnszone.com
ipa: ERROR: Nameserver 'zippyvm2.testrelm.com.' does not have a corresponding A/AAAA record

[[br]]Additional info:
[[br]]zippyvm2.testrelm.com does have a A record.

{{{
[root@zippyvm2 ipa-dns]# ipa dnsrecord-find testrelm.com zippyvm2
  Record name: @
  NS record: zippyvm2.testrelm.com.

  Record name: zippyvm2
  A record: 10.14.5.134
  SSHFP record: 1 1 2C0B9281ADBB3F584717C0A0D4508B058FB27ADE, 2 1 B6D4C452A34CCE9A92BD374D497115AF39A16783
}}}
Comment 1 Rob Crittenden 2012-10-26 13:49:50 UTC 
Tomas has been unable to reproduce this, see the ticket for details.

Can you re-test this?
Comment 2 Namita Soman 2012-11-02 15:22:59 UTC 
We see this intermittently. will ping Tomas when we see it again
Comment 3 Tomas Babej 2012-11-29 17:53:07 UTC 
I was not able to reproduce this on QA machine using automated DNS tests (where the issue originally came from) multiple (10+) times during the last weekend on current nightly build. QA is to run whole test suite and determine whether the bug can be verified.
Comment 4 Namita Soman 2012-11-29 18:04:19 UTC 
Will mark this verified for now. tests were done using ipa-server-3.0.0-8.el6.x86_64
Comment 6 Tomas Babej 2012-12-05 15:32:07 UTC 
I got hold of the machine where the issue is reproducible. Turns out this comes up when the server is not configured to look at its own DNS records (probably because /etc/resolv.conf was rewritten by a network tool). Adding nameserver 127.0.0.1 to /etc/resolv.conf and restarting solves the issue.
Comment 8 errata-xmlrpc 2013-02-21 09:19:49 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.