automatic reverse and forwarding zones
Havard Eidnes
he at uninett.no
Thu Oct 27 10:06:28 UTC 2022
> > To "fill" an ip6.arpa zone for a /64 requires 18446744073709551616
> > records (yes, that's about 18 x 10^18 if my math isn't off). I predict
> > you do not posess a machine capable of running BIND with that many
> > records loaded -- I know we don't.
>
> It sure would be nice to be able to set some kind of default
> (static) answer for reverse zones. While it has limited
> useability for IPv4, it would actually be nice, and it seems a
> win for IPv6 reverse.
That's what you get with a wildcard PTR record, e.g.
*.0.0.0.0.e.d.0.c.d.a.b.0.1.0.0.2.ip6.arpa. IN PTR whatevername.your-domain.
would return "whatevername.your-domain." as a PTR record whenever
an otherwise-nonexistent PTR record in the
0.0.0.0.e.d.0.c.d.a.b.0.1.0.0.2.ip6.arpa.
zone was queried for.
> It probably does not play well with DNSSEC [...]
Oh, it does. This is what the "labels" field in the RRSIG record
is for, ref.
https://www.rfc-editor.org/rfc/rfc4034.html#page-8
Regards,
- Håvard
More information about the bind-users
mailing list