Dear Andrius, Andrius Kasparavicius wrote:
hi, why there is no "nameserver" records in inet6num? Also it would be
"nameserver:" attribute can appear in the "domain" object representing delegation. "inetnum" and "inet6num" objects contain optional "rev-srv:" attribute, that is not used in RIPE NCC's reverse delegation process.
useful to have reverse zones on ftp.ripe.net, like in-addr now is. Also,
That can be done, though at some point we'd prefer to see the RIPE Database as a single and authoritative source of this information (apart from DNS itself of course). To facilitate this a "-d" flag was introduced in the database allowing one to walk up and down the reverse domains tree using an IP address as a search key. For instance: whois -dr -Tdomain 2001:778::/32 % This is the RIPE Whois server. % The objects are in RPSL format. % % Rights restricted by copyright. % See http://www.ripe.net/ripencc/pub-services/db/copyright.html domain: 7.0.1.0.0.2.ip6.arpa [...] One can also use -MmlL modifiers.
maybe could someone explain why dig -x 2001:778:: NS doesn't work? Is it my fault?
If you are the holder of 2001:778::/32 allocation you may request reverse delegation for this space following the procedure http://www.ripe.net/ripencc/mem-services/registration/reverse/ipv6.html
best regards, Andrius
Regards, Andrei Robachevsky CTO, RIPE NCC