Bug 856293 - Nameserver does not have a corresponding A/AAAA record while creating new dns zone
Nameserver does not have a corresponding A/AAAA record while creating new dns...
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa (Show other bugs)
Unspecified Unspecified
medium Severity unspecified
: rc
: ---
Assigned To: Rob Crittenden
Namita Soman
Depends On:
  Show dependency treegraph
Reported: 2012-09-11 12:39 EDT by Dmitri Pal
Modified: 2013-02-21 04:19 EST (History)
6 users (show)

See Also:
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.
Story Points: ---
Clone Of:
Last Closed: 2013-02-21 04:19:49 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2013:0528 normal SHIPPED_LIVE Low: ipa security, bug fix and enhancement update 2013-02-21 03:22:21 EST

  None (edit)
Description Dmitri Pal 2012-09-11 12:39:10 EDT
This bug is created as a clone of upstream ticket:

[[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]]How reproducible:

[[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:
  SSHFP record: 1 1 2C0B9281ADBB3F584717C0A0D4508B058FB27ADE, 2 1 B6D4C452A34CCE9A92BD374D497115AF39A16783
Comment 1 Rob Crittenden 2012-10-26 09:49:50 EDT
Tomas has been unable to reproduce this, see the ticket for details.

Can you re-test this?
Comment 2 Namita Soman 2012-11-02 11:22:59 EDT
We see this intermittently. will ping Tomas when we see it again
Comment 3 Tomas Babej 2012-11-29 12:53:07 EST
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 13:04:19 EST
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 10:32:07 EST
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 to /etc/resolv.conf and restarting solves the issue.
Comment 8 errata-xmlrpc 2013-02-21 04:19:49 EST
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.


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