Sorry for the bad formatting...

b._dns-sd._udp  IN PTR @
lb._dns-sd._udp IN PTR @

_http._tcp      IN PTR Some\ Web\ Page._http._tcp Some\ Web\ Page._http._tcp SRV 0 0 80 neinfo.example.com.
                                                                             TXT path=/

I agree. Currently an attempt to add PTR record to non-arpa zone fails with following error:

invalid 'ptrrecord': Reverse zone for PTR record should be a sub-zone of one the following fully qualified domains: ip6.arpa., in-addr.arpa.

This should be just a warning like:

PTR records typically exist in a sub-domains of one the following fully qualified domains: ip6.arpa., in-addr.arpa.

Even better, we might show the warning only if node name does not contain an underscore to avoid false positives caused by DNS-SD.

We need this functionality for a managed printing (over DNS-SD) on MasOS clients in our network.

Or have any workaround for add non-standart PTR-records in managed FreeIPA DNS-server?

similar issue: https://pagure.io/freeipa/issue/7171

For reference, the DNS-SD RFC: https://tools.ietf.org/html/rfc6763.

IMO we should just remove the error and not even bother with a warning.
There are possible uses for PTR that we might not even know about. And
if you're creating PTR records, you (hopefully) know what you're doing...

I'll close #7171 as duplicate.

You can add records by manually editing items in ldap

It may be true that there are lots of users for all kinds of records but being a general-purpose DNS server was never the goal.

@rcritten it seems like a legitimate use case to me. We don't even have to add functionality, just get out of the way.

I want to boost this. Looking at DNS-SD for ACME service discovery. I might just go ahead and produce the PR.

PR: https://github.com/freeipa/freeipa/pull/5239

master:

• b153b23 dns: allow PTR records in arbitrary zones

ipa-4-8:

• 82a581d dns: allow PTR records in arbitrary zones