[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
IPV6 in enterprise best practices/white papaers
- Subject: IPV6 in enterprise best practices/white papaers
- From: seth.mos at dds.nl (Seth Mos)
- Date: Sat, 26 Jan 2013 22:30:43 +0100
- In-reply-to: <CAP-guGX01KLj2cG3ASmfXbmpxZ6j=i1b0DZ++s4-W8Uq_vy-5Q@mail.gmail.com>
- References: <CAKb_Nupf4GAY4cFnyyb3hewFCWk6Vp4zLyyKnc4ct-0T4K356A@mail.gmail.com> <CAP-guGX01KLj2cG3ASmfXbmpxZ6j=i1b0DZ++s4-W8Uq_vy-5Q@mail.gmail.com>
Op 26 jan 2013, om 18:47 heeft William Herrin het volgende geschreven:
> On Sat, Jan 26, 2013 at 4:26 AM, Pavel Dimow <paveldimow at gmail.com> wrote:
>> I can start to create
>> AAAA record and PTR recors in DNS and after that I should configure my
>> dhcp servers and after all has been done I can test ipv6 in LAN and
>> after that I can start configure bgp with ISP.
>> Is this correct procedure?
>
> Nope.
>
> In their infinite(simal) wisdom the architects of IPv6 determined that
> a host configured with both a global scope IPv6 address and an IPv4
> address will attempt IPv6 in preference to IPv4. If you configure IPv6
> on a LAN without first installing your IPv6 Internet connection, that
> LAN will break horribly.
>
> Work your way from the outside in: start with BGP, then the interior
> routers and configure the LAN last.
+3
That's what I did too, it works the best, you really need to make sure that the connectivity you turn up actually works. I started with the internet connections, and luckily HE.net also offers free BGP tunnels for PI connectivity, which will do in a pinch and you still can maintain redundancy of only 1 ISP can actually do native yet.