Bug in ptrrecord validation causes that PTR for IPv6 is no accepted when domain name is absolute
$ ipa dnsrecord-add e.4.2.2.0.0.0.0.2.5.0.0.0.2.6.2.ip6.arpa. 2.3.4.1.3.2.e.f.f.f.a.4.a.1.2.0.e.4.2.2.0.0.0.0.2.5.0.0.0.2.6.2.ip6.arpa. --ptr-rec=example.com. ipa: ERROR: invalid 'ptrrecord': Reverse zone ip6.arpa. requires exactly 32 IP address components, 51 given
Relative domain works
$ ipa dnsrecord-add e.4.2.2.0.0.0.0.2.5.0.0.0.2.6.2.ip6.arpa. 2.3.4.1.3.2.e.f.f.f.a.4.a.1.2.0 --ptr-rec=example.com Record name: 2.3.4.1.3.2.e.f.f.f.a.4.a.1.2.0 PTR record: example.com
Please note that error should be also turn into warning and check should be fixed.
mbasti: works for me for IPv4 (but I may test it wrong) I suggest to migrate this check to warning, PTR are not limited to just IP addresses in general [pspacek] agree, turn the error into warning
Metadata Update from @mbasti: - Issue assigned to mbasti - Issue set to the milestone: FreeIPA 4.5 backlog
Metadata Update from @mbasti: - Issue assigned to tkrizek (was: mbasti) - Issue close_status updated to: None
Metadata Update from @tkrizek: - Assignee reset
Login to comment on this ticket.