On 06/12/2017 11:28 AM, Martin Bašti wrote:


On 11.06.2017 01:20, John Morris via FreeIPA-users wrote:
This works to find a single DNS record:

    $ ipa dnsrecord-find example.com --name=ipa-ca --pkey-only
      Record name: ipa-ca
    ----------------------------
    Number of entries returned 1
    ----------------------------

But this fails to find the origin record:

    $ ipa dnsrecord-find example.com --name=@ --pkey-only
    ----------------------------
    Number of entries returned 0
    ----------------------------

It appears that the origin record is only treated inconsistently in
`dnsrecord-find`; other dnsrecord commands work fine in the form
`dnsrecord-* example.com @`.

How does one find ONLY for a zone's origin record?

Thanks-

    John
_______________________________________________
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org
To unsubscribe send an email to
freeipa-users-le...@lists.fedorahosted.org

Hello,

why do you need a find for zone apex? There is always exactly one, you
can use `ipa dnsrecord-show example.com. @`  OR `ipa dnsrecord-show
example.com. example.com.`

What is your use case?

Martin

Hi Martin,

I've been adding some classes to the Ansible IPA modules. The existing IPA modules use the `*_find` API method to locate existing objects. I'm not sure why the original author doesn't use the `*_show` method, unless it's to allow for non-unique search keys, or if the `*_show` method doesn't exist for some object types.

Sounds like the answer is there's no equivalent to `dnsrecord-find zone.tld @` that will find the zone origin record. I'll write a workaround. Thanks-

        John
_______________________________________________
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org

Reply via email to