--- JORDI PALET MARTINEZ <[EMAIL PROTECTED]>
wrote:
>
> But as said, IPv6 was designed having in mind a
> smooth transition including
> dual-stack. Nothing is wrong when IPv6 "alone"
> doesn't work today. Is like
> trying to use only gas in an engine that requires a
> mix of gas and oil. It
> is
backup monitoring via ipv6 and network monitoring via ipv6 now
required for big telco in UK so that testing can be done before
implementation.
I guess quite a few networks will be both ipv4-ipv6 type for a long
long time :)
Colin
Below, in-line.
Regards,
Jordi
> De: Stephen Wilcox <[EMAIL PROTECTED]>
> Responder a: <[EMAIL PROTECTED]>
> Fecha: Sat, 30 Jun 2007 14:23:37 +0100
> Para: JORDI PALET MARTINEZ <[EMAIL PROTECTED]>
> CC:
> Asunto: Re: IPv6 & DNS
>
>
> On Fri, Jun 29, 2007 at 06:57:30PM -0400, JORDI PALET MA
I don't see the problem. I've deployed IPv6 in may web servers, and nothing
failed, we had firewall support for IPv6 most of the time, and otherwise we
used iptables6. The DNS thing has been replied already as I can see.
I think we have lots of documents on-line explaining all this, including our
On Fri, Jun 29, 2007 at 06:57:30PM -0400, JORDI PALET MARTINEZ wrote:
>
> This is one more reason, some OSs may not support IPv6 DNS transport, so you
> need to keep dual stack.
The OS, IPv6, udp/tcp and DNS are all at different layers of the protocol
stack.. we are supposed to be able to seaml
On 30-jun-2007, at 7:04, Stephen Satchell wrote:
That includes DNS, by the way. I'm deploying new DNS servers, and
would be *very* interested in how to convince BIND 9.2.4 to answer
IPv6 queries.
If you give the box BIND runs on an IPv6 address, it'll use IPv6 to
perform queries when re
6 matches
Mail list logo
