Bug 1108202

Summary:	dnsrecord-* with absolute target gives error
Product:	Red Hat Enterprise Linux 7	Reporter:	Martin Kosek <mkosek>
Component:	ipa	Assignee:	Martin Kosek <mkosek>
Status:	CLOSED ERRATA	QA Contact:	Namita Soman <nsoman>
Severity:	unspecified	Docs Contact:
Priority:	medium
Version:	7.1	CC:	rcritten
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ipa-4.0.3-1.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-05 10:11:20 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 Martin Kosek 2014-06-11 14:47:58 UTC

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/freeipa/ticket/4232

For example:
{{{
$ ipa dnsrecord-add testdomain.com. testdomain.com. --mx-rec="5 mx.testdomain.com."
ipa: ERROR: invalid 'name': empty DNS label
}}}

It is complaining about the second "testdomain.com.".

The workaround is to use a "@" (for the domain itself) or a relative name e.g.

{{{
$ ipa dnsrecord-add testdomain.com. @ --mx-rec="5 mx.testdomain.com."
# testdomain.com. MX 5 mx.testdomain.com.
$ ipa dnsrecord-add testdomain.com. subdomain --mx-rec="5 mx.testdomain.com."
# subdomain.testdomain.com. MX 5 mx.testdomain.com.
}}}

Comment 1 Martin Kosek 2014-06-11 15:23:25 UTC

This request is already fixed in upstream FreeIPA project. Please refer to the linked ticket for additional details and related commits.

Comment 3 Namita Soman 2015-01-26 18:13:23 UTC

Verified using ipa-server-4.1.0-16.el7.x86_64


# ipa dnsrecord-add testrelm.test. testrelm.test. --mx-rec="5 mx.testrelm.test."
  Record name: @
  MX record: 5 mx.testrelm.test.
  NS record: cloud-qe-14.testrelm.test., cloud-qe-3.testrelm.test.

Comment 5 errata-xmlrpc 2015-03-05 10:11:20 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.

https://rhn.redhat.com/errata/RHSA-2015-0442.html