Bug 690946 - kx records created with dnsrecord-add not resolvable with dig
Summary: kx records created with dnsrecord-add not resolvable with dig
Keywords:
Status: CLOSED DUPLICATE of bug 689648
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ipa
Version: 6.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Rob Crittenden
QA Contact: Chandrasekar Kannan
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-25 21:50 UTC by Michael Gregg
Modified: 2015-01-04 23:47 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-08-31 20:12:59 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 689648 1 None None None 2021-01-20 06:05:38 UTC

Internal Links: 689648

Description Michael Gregg 2011-03-25 21:50:42 UTC 
Description of problem:
kx records created with dnsrecord-add not search-able with dig. 

Version-Release number of selected component (if applicable):
ipa-admintools-2.0.0-16.el6.x86_64

How reproducible:
always

Steps to Reproduce:
1. Create a new zone $zone
2. ipa dnsrecord-add $zone @ --kx-rec "12345678 $zone"
3. dig kx $zone
  
Actual results:
dig give a record not found

Additional info:
As a kx record is new to me, I'm pretty sure these records go in the @ zone. 
I'm working off of this rfc for reference:
http://tools.ietf.org/html/rfc2230

I also tried creating a separate kx.$record to search against, with no luok.
Comment 5 Martin Kosek 2011-08-31 20:12:59 UTC 
Closing as duplicate of 689648 so that we can deal with this issue at one place. The root cause is the same as in 689648.

*** This bug has been marked as a duplicate of bug 689648 ***
Note You need to log in before you can comment on or make changes to this bug.