On Tue, Apr 12, 2011 at 11:21:14AM +0200, Marco Davids (SIDN) wrote:
...
> Or do it 'the BIND way':
>
> dig -x 2001:7b8:c05::80:1 | grep ip6.arpa | tail -1 | awk '{print $1}'
...
If things work right, this seems to give the name of the smallest
existing enclosing zone (from the SOA or NS record), not the entry in
the zone. Wasn't the latter what was desired? And what if you are
creating the new zone?
As 'arpaname' given the above, returns:
1.0.0.0.0.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0.5.0.C.0.8.B.7.0.1.0.0.2.IP6.ARPA
then the entry
1.0.0.0.0.8.0.0.0.0.0.0.0.0.0.0.0.0.0.0 PTR sidn.bip.bit.nl.
in the 5.0.c.0.8.b.7.0.1.0.0.2.ip6.arpa. zone file
("zone.2001:07b8:0c05"?) may be the best we can do in general.
In specific, we could enter:
$ORIGIN 0.0.0.0.0.0.0.0.0.0.0.0
1.0.0.0.0.8.0.0 PTR sidn.bip.bit.nl.
...
$ORIGIN 5.0.c.0.8.b.7.0.1.0.0.2.ip6.arpa.
if we have multiple addresses in that subnet.
But M. de Nostredame already is aware of how to do this.
Using one of the existing IPAM (IP Address Management) appliances might
be what you need. BT has one that looked good.
--
/*********************************************************************\
**
** Joe Yao j...@tux.org - Joseph S. D. Yao
**
\*********************************************************************/
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
