Bug 671274

Summary: unable to add MX records with dns2 tools
Product: [Fedora] Fedora Reporter: Michael Gregg <mgregg>
Component: freeipaAssignee: Rob Crittenden <rcritten>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: atkac, ayoung, dpal, mkosek, rcritten, ssorce
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-19 15:15:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Michael Gregg 2011-01-20 23:07:42 UTC 
Description of problem:
unable to add MX records with dns2 tools

Version-Release number of selected component (if applicable):
ipa-server-2.0-0.2011011418gita68b2d2.fc14.x86_64

How reproducible:
always

Steps to Reproduce:
Trying to add a mx record to the testrelm domain
I tried:
ipa dnsrecord-add testrelm  --mx-rec=1.2.3.4
 
I even tried
ipa dnsrecord-add testrelm mx --mx-rec=1.2.3.4
 
dig testrelm MX
and
dig mx.testrelm MX
 
matches no results.
Comment 1 Michael Gregg 2011-01-20 23:17:33 UTC 
I just realized what the correct syntax to add a MX record should be, but it still does not seem to work.

This part works:
ipa  dnsrecord-add newzone1 @ --mx-rec=3.4.5.6
  Record name: newzone1
  MX record: 3.4.5.6
  NS record: 10.16.98.193.

I am still unable to look that record up.
"dig newzone1 MX" returns nothing.
Comment 4 Simo Sorce 2011-01-21 01:08:40 UTC 
Looks like a bind_dyndb_ldap tool.
The data is in ldap, but named does not return it.

Also if I set the MX record on the zone record itself (as it should be), then dig stops returing the SOA information.
Comment 5 Simo Sorce 2011-01-21 01:10:49 UTC 
I meant bind-dyndb-ldap *bug* of course :)
Comment 6 Adam Tkac 2011-02-14 13:28:54 UTC 
The MX record in the original description is invalid.

MX record format is following (check for example RFC 1035, section 5.3):

MX <priority> <mailserver_FQDN>

So correct addition of MX record is, for example:

ipa dnsrecord-add testrelm mx --mx-rec="10 mail.testrelm."

This way MX record is added correctly and is also visible via dig utility.
Comment 8 Adam Tkac 2011-02-14 13:33:15 UTC 
Reassigning to freeipa component to inspect if "ipa" CLI should be improved someway.
Comment 9 Dmitri Pal 2011-02-15 06:46:18 UTC 
https://fedorahosted.org/freeipa/ticket/967
Comment 10 Martin Kosek 2011-07-27 13:51:29 UTC 
Already fixed upstream:
master: https://fedorahosted.org/freeipa/changeset/a9dc175bc547996646c213661ca42906ffef83ab
Comment 11 Rob Crittenden 2011-10-19 15:15:25 UTC 
Fixed in IPA v2 RC 2 (2.0.0.rc2)