[129629] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Reverse DNS for IPv6 client networks

daemon@ATHENA.MIT.EDU (Owen DeLong)
Tue Sep 14 11:14:03 2010

From: Owen DeLong <owen@delong.com>
In-Reply-To: <20100914122758.GK63203@ronin.4ever.de>
Date: Tue, 14 Sep 2010 08:08:45 -0700
To: "Elmar K. Bins" <elmi@4ever.de>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org


On Sep 14, 2010, at 5:27 AM, Elmar K. Bins wrote:

> Hi guys,
>=20
> I am looking for operational experience here.
>=20
> We have just turned up IPv6 in our "guest wireless", by way of using =
RA
> for address distribution and DHCPv6 for the DNS server address =
(stupid, yup).
>=20
> Apart from the dhcp6 part seemingly not working on Juniper ISGs (or =
maybe it's
> my windows *and* that Ubuntu), I now see IPv6 addresses instead of =
names.
>=20
> I as a networking droid have not much quarrel with that, but I am =
interested
> in how or whether at all others handle this.
>=20
> Are you creating DNS entries somehow (reverse and, ultimately, =
forward),
> are you using BIND "generate" statements, are you using wildcards...or
> are you just ignoring this for the "dynamic boxes"?
>=20
> Please enlighten me!
>=20
> Elmar.

I would strongly discourage $GENERATE statements... You won't have =
enough
memory or even disk space to hold the results.

I think the choices are either live with numbers, use a  wildcard, or =
use dynamic
DNS name registration.

Owen



home help back first fref pref prev next nref lref last post