PTR resolution not support set individual zonefiles for subnets like /25.

[zelenezhang]

PTR resolution not support set individual zonefiles for subnets like /25, which is defined by RFC2371(Classless IN-ADDR.ARPA delegation) and support by Bind9

for example: I want to manage PTR RR of IP in 192.168.1.0/25 with individual zonefile, but i cannot get PTR result with dig -x 192.168.1.10, dig -x 192.168.1.128 is ok
zonefile config like below
parent zonefile

$ORIGIN 1.168.192.in-addr.arpa.
$TTL 86400
@ IN SOA ns1.example.com. admin.example.com. (
    2023082001 ; Serial
    3600       ; Refresh
    1800       ; Retry
    604800     ; Expire
    86400      ; Minimum TTL
   )

@ IN NS ns1.example.com.
@ IN NS ns2.example.com.

128 IN PTR host128.example.com.
; delegation subnet 192.168.1.0/25 to subzone
0/25 IN NS ns1.subnet.example.com.

sub-zone zonefile

$ORIGIN 0/25.1.168.192.in-addr.arpa.
$TTL 86400
@ IN SOA ns1.subnet.example.com. admin.subnet.example.com. (
    2023082001 ; Serial
    3600       ; Refresh
    1800       ; Retry
    604800     ; Expire
    86400      ; Minimum TTL
   )

; 配置PTR记录
10 IN PTR host10.subnet.example.com.
11 IN PTR host11.subnet.example.com.

[wcawijngaards]

It looks like this is some sort of extension that generates zone file contents for you. Specifically it enumerates a list of names and then creates CNAMEs, DNAMEs, or PTR records, I guess. That is usually what people use for creating reverse zones, I think. So that generated content is not in the zone file and would need to be added to make the lookup work.

The lookup in the zone that is called 0/25.1.168.192.in-addr.arpa. should work, for a lookup of 10.0/25.1.168.192.in-addr.arpa. PTR. But in the post the lookup of -x 192.168.1.10, is a name that does not end in the zone name 0/25.1.168.192.in-addr.arpa., it looks up 10.1.168.192.in-addr.arpa..