|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |
From: Owen DeLong <owen@delong.com> In-Reply-To: <5A6D953473350C4B9995546AFE9939EE0BC1361D@RWC-EX1.corp.seven.com> Date: Wed, 26 Jan 2011 10:47:41 -0800 To: "George Bonser" <gbonser@seven.com> Cc: nanog@nanog.org Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org On Jan 26, 2011, at 10:39 AM, George Bonser wrote: > > >> From: Charles N Wyble >> Sent: Wednesday, January 26, 2011 10:23 AM >> To: nanog@nanog.org >> Subject: Ipv6 for the content provider >> >> 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 :) > > > Most load balancers these days will allow you to provision an IPv6 > virtual IP that balances to v4 servers. So you can provide services > over v6 without a lot of changes inside your network. You will need a > DNS server that hands out AAAA records though. > > And if your servers behind the LB aren't prepared for it, you lose a LOT of logging data, geolocation capabilities, and some other things if you go that route. Owen
|
|
|
|
|
|
|
|
|
|
|
|
| home | help | back | first | fref | pref | prev | next | nref | lref | last | post |