#1114 mx records not searchable with dnsrecord-find or dig
Closed: Fixed None Opened 9 years ago by dpal.

Adding an MX record requires a named restart

ipa dnsrecord-add example.com @ --mx-rec "10 l.z.com"

ipa dnsrecord-show example.com @

Record name: @
MX record: 10 l.z.com
NS record: slinky.example.com.

service named restart

dig example.com MX

; <<>> DiG 9.7.3-RedHat-9.7.3-1.fc14 <<>> example.com MX
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6978
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 1

;example.com. IN MX

example.com. 86400 IN MX 10 l.z.com.example.com.

example.com. 86400 IN NS slinky.example.com.

slinky.example.com. 86400 IN A

;; Query time: 5 msec
;; WHEN: Wed Apr 27 13:41:47 2011
;; MSG SIZE rcvd: 90

I also tested adding an mx record with a trailing dot and it looks better:

example.com. 86400 IN MX 10 l.z.com.
example.com. 86400 IN MX 10 l.z.com.example.com.

An MX record is stored within the zone which is why ipa dnsrecord-find can't find it. Use ipa dnszone-show example.com @

Implementation for FreeIPA part is ready. Waiting for bind-dyndb-ldap features that the patch depends on to be completed. Pushing to July milestone.

Moving to the next milestone - changes to bind-dyndb-ldap are not done yet.

Will be resolved with documentation fix in ticket #1709.

A complete resolution of this ticket would require a full persistent search feature of bind-dyndb-ldap proposed in #649.

After fix of current zone-only persistent search in bind-dyndb-ldap, this attribute is refreshed immediately when DNS is configured with persistent search (#826).

If persistent search feature is not feasible, please refer to information in the doc (updated in #1709). If psearch is off, one has to wait for bind-dyndb-ldap cache to expire (the doc specifies how to control it).

Metadata Update from @dpal:
- Issue assigned to mkosek
- Issue set to the milestone: FreeIPA 2.1.1 (bug fixing)

3 years ago

Login to comment on this ticket.