What is the correct format for IPv6 PTR records?

English Network/Internet
1

BIND named 9.20.29
linux v6.12.0-160000.38-default x86_64
ID=“opensuse-leap”
VERSION_ID=“16.0”

I have searched various sites that offer details regarding the format for an IPv6 PTR entry. There is even one that takes a IPv6 string and creates the PTR text.

named complains thusly:

PTR entry:
1.0.5.4.8.a.0.c.0.0.0.0.0.0.0.0.c.3.f.3.f.1.2.5.0.6.7.4.f.2.d.f.ip6.arpa. 3600  IN   PTR     sma-gateway1.sma.com.

yields the warning:
09-Oct-2026 21:20:54.320 general: warning: master/69.168.192.rev:57: ignoring out-of-zone data (1.0.5.4.8.a.0.c.0.0.0.0.0.0.0.0.c.3.f.3.f.1.2.5.0.6.7.4.f.2.d.f.ip6.arpa)
2

https://www.google.com/search?q=ignoring+out+of+zone+data+reverse+dns

3

I did do a search for an answer before asking the forum. According to your references as well, the example PTR should be accepted. It is not. I have tried the IP text with a trailing dot (.) and without a dot.

Note the question is about a reverse name record. Almost all of the search results are for forward records.

4

The BIND warning gives the clue: ignoring out-of-zone data. The PTR record is for IPv6 (ip6.arpa), but you added it to an IPv4 reverse zone file (69.168.192.rev). It needs to be defined in the appropriate IPv6 reverse zone.

Maybe this helps…

5

Yes, that is what is happening.
I created another zone and files for IPv6. It works!

2 Likes
6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.