Ipv6 for the content provider

Jack Carrozzo jack at crepinc.com
Wed Jan 26 18:38:48 UTC 2011


Bind and apache work with v6 out of the box, and have for years. As I
understand it, when a client requests a particular domain of yours and gets
an A and an AAAA, the client will default to the AAAA (assuming it's on a v6
network) and attempt to communicate as such. Failing that, it will fall back
to the v4 A record.

So in short, yes, it's as simple as telling the daemons to listen on your v6
addresses and adding the AAAA records. Just think how happy your 1
client/customer using IPv6 will be ;-)

-Jack Carrozzo

On Wed, Jan 26, 2011 at 1:22 PM, Charles N Wyble
<charles at knownelement.com>wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hello,
>
>
> All the recurring threads about prefix length, security posture, ddos,
> consumer CPE support have been somewhat interesting to my service
> provider alter ego. Ipv6 is definitely on folks minds this year. The
> threads seem a lot less trollish as well. It appears some significant
> progress is being made, and peoples opinions are firming up. Hopefully
> this will help move ipv6 adoption forward.
>
> I have recently turned up an ipv6 tunnel with he.net and have end to end
> connectivity. I'm using pfsense as my routing platform. It was pretty
> easy (about 10 minutes of total work I think). So I can connect to
> various ipv6 enabled sites on the interwebz. This seems to be the first
> step in deployment.
>
>
> For the most part, I'm a data center/application administrator/content
> provider kind of guy. As such, I want to provide all my web content over
> ipv6, and support ipv6 SMTP.  What are folks doing in this regard?
>
> Do I just need to assign ip addresses to my servers, add AAAA records to
> my DNS server and that's it? I'm running PowerDNS for DNS, Apache for
> WWW. Postfix for SMTP.
>
> Feel free to point me at any good manuals and say RTFM :)
>
>
>
> - --
> Charles N Wyble (charles at knownelement.com)
> Systems craftsman for the stars
> http://www.knownelement.com
> Mobile: 626 539 4344
> Office: 310 929 8793
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iQIcBAEBAgAGBQJNQGZvAAoJEMvvG/TyLEAt9ykP/ROLSWz3LmAF78OMBEhWEMvX
> MjOVR2QK6kQ3byV8WLro95tCOuyo8L8fUC60KyFh4XRsedb7xk6S8cTER80zmGzG
> rOAFVpNyJ1QzCcf4MYpj8xHn9zM6Fywft4VzKQEgDvlV8yD0VZKJi+fNj4noZ5oK
> tmM1s9Is5db3d5ldrC6M54TQJsbaZiuz+FrFtpkENraJIWlOeU3laM6kvwzvYpok
> BKtnaY6zBq42QovpJ+MU+lmanCB6Z0r3e2cSB+N7XJL0Va/Y2IW/eZn35S+dE3xk
> y7RPSZu2jDxJ6atQJVIBpjfL6oqUUr+0RHc+gX4VJyOrwpEuJQ/GvTiRDTUZkA0A
> twhvQnS6yc5G8L+iwID4YqkVKNCFcJUtAHUntqmy1FqTe9iQSlZdUPPhKrkRE7zW
> B2S2T0Lv6a/neHU5yfsGjiYbIAy7keXoiMPbR4ZJxC/KkogfWNgMZBVpjGVn0NI4
> COOymyFYgvQFiXIpvmpQn0iLFcWmmGdwV2DPvxMArdmfw2SeyipJiBSeeEbb4ZG4
> kw1LOrI7+OGnoDEByAtkZPh42wAbXbrSw9WeWvphAsQ2dAmASqXUKuHTDXd1laCC
> yi37NTRmWACNHKcVEhpk3saJDCsPPVx6ECYfhSsSALZDn6696BvFXZnN2423Fmk7
> dtMKM38+rxz9r4IL5O+n
> =Mi6R
> -----END PGP SIGNATURE-----
>
>



More information about the NANOG mailing list