Bug 690946

Summary:	kx records created with dnsrecord-add not resolvable with dig
Product:	Red Hat Enterprise Linux 6	Reporter:	Michael Gregg <mgregg>
Component:	ipa	Assignee:	Rob Crittenden <rcritten>
Status:	CLOSED DUPLICATE	QA Contact:	Chandrasekar Kannan <ckannan>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1	CC:	benl, dpal, mkosek
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-08-31 20:12:59 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 ***