gistfile1.txt

Just to demonstrate that the problem of mixing data between different zones in the same file is
just as relevant for completely static records, and is found by the normal named-checkzone tool (as well as named-checkconf -z):

$ cat >test.zone
$TTL 7200
@ IN SOA ns.example.com. hostmaster.example.com. 1 3600 1800 3600000 7200
@ IN NS ns.example.com.
$ORIGIN 0.222.92.in-addr.arpa.
1 IN PTR fr-edge-hsrp-be20-2001.example.net.

$ /usr/sbin/named-checkzone 0.222.92.in-addr.arpa. test.zone
zone 0.222.92.in-addr.arpa/IN: loaded serial 1
OK

$ /usr/sbin/named-checkzone 1.222.92.in-addr.arpa. test.zone
test.zone:5: ignoring out-of-zone data (1.0.222.92.in-addr.arpa)
zone 1.222.92.in-addr.arpa/IN: loaded serial 1
OK
$

yes, thank you, that explain all:

test-file
$TTL 7200
@ IN SOA ns.example.com. hostmaster.example.com. 1 3600 1800 3600000 7200
@ IN NS ns.example.com.
$ORIGIN 0.222.92.in-addr.arpa.
1 IN PTR fr-edge-hsrp-be20-2001.example.net.
$ORIGIN 1.222.92.in-addr.arpa.
1 IN PTR fr-edge-hsrp-be20-2001.example.net.

# named-checkzone 1.222.92.in-addr.arpa. test-file
test-file:5: ignoring out-of-zone data (1.0.222.92.in-addr.arpa)
zone 1.222.92.in-addr.arpa/IN: loaded serial 1
OK

named-checkzone 0.222.92.in-addr.arpa. test-file
test-file:7: ignoring out-of-zone data (1.1.222.92.in-addr.arpa)
zone 0.222.92.in-addr.arpa/IN: loaded serial 1
OK