Hi, On Mon, Apr 08, 2024 at 12:10:57PM +0200, Alessandro Vesely wrote:
Thanks, that apparently works. However, -T domain -d 2a02:: finds 0.0.0.0.2.0.a.2.ip6.arpa. It seems to prepend a variable number of zeroes and cite the wrong name servers (see queries below). Shouldn't it find 2.0.a.2.ip6.arpa? That domain exists, although it has no name servers.
0.a.2.ip6.arpa is the RIPE's "top level" reverse zone, and I would assume that these need to be entered manually into the DNS system (because it's not "a child zone of an existing zone"). Like you need to add your IP blocks to your IPAM, to be able to allocate a subnet from it. So 0.0.0.0.2.0.a.2.ip6.arpa seems to be the first "customer" DNS delegation from there.
The parent zone, 0.a.2.ip6.arpa, has lots of international NSes, none of which matches the ones returned by the database queries.
Delegations don't seem to be generated from the database. How is that supposed to work?
They are, but maybe not for the highest level. Like, 8.0.6.0.1.0.0.2.ip6.arpa - that's our space, 2001:608::/32, and the reverse DNS delegation was done (back then, in August 2002) via the DB entry, and I'm assured it still works that way. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Ingo Lalla, Karin Schuler Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279