From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] IPv6 not ready here; Hmmm
Date: Wed, 8 Jun 2011 22:08:03 +0200 [thread overview]
Message-ID: <201106082208.04183.alan.mckinnon@gmail.com> (raw)
In-Reply-To: <BANLkTi=Py8G3HuxMKo7VB3iF2rgw+_H78A@mail.gmail.com>
Apparently, though unproven, at 21:45 on Wednesday 08 June 2011, Paul Hartman
did opine thusly:
> On Tue, Jun 7, 2011 at 8:27 PM, Dale <rdalek1967@gmail.com> wrote:
> > Funny thing is, I use googles DNS servers. 8.8.8.8 and 8.8.4.4 are the
> > settings. I find it ironic that Google is one of the ones hosting this
> > event and it appears their server is not ready. Makes me think. < Dale
> > scratches chin a bit >
>
> From Google DNS FAQ:
>
> Does Google Public DNS support IPv6?
> Google Public DNS can respond to requests for IPv6 addresses (AAAA
> requests), but it does not yet support native IPv6 transport and
> cannot talk to IPv6-only authoritative nameservers. Clients should use
> IPv4 network connections to use Google Public DNS.
Almost all large auth servers out there are in exactly that position. Mine
certainly are. Cisco are waiting in the wings with a gigantic[1] quote for
what it will take to change that.
[1] When I say "gigantic" I really do mean "gigantic", as in "OMFG, does the
number of $US fit into the money field in Oracle Financials??". Not "gigantic"
as in "oh, that's big, bigger than what we normally call big".
Just wanted to add some perspective...
--
alan dot mckinnon at gmail dot com
next prev parent reply other threads:[~2011-06-08 20:10 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 1:27 [gentoo-user] IPv6 not ready here; Hmmm Dale
2011-06-08 1:53 ` Dale
2011-06-08 2:18 ` Adam Carter
2011-06-08 5:31 ` Mick
2011-06-08 5:29 ` [gentoo-user] " Hans de Graaff
2011-06-08 17:01 ` [gentoo-user] " Volker Armin Hemmann
2011-06-08 18:59 ` Dale
2011-06-09 3:25 ` Volker Armin Hemmann
2011-06-09 4:56 ` Dale
2011-06-09 6:59 ` Volker Armin Hemmann
2011-06-08 19:51 ` Paul Hartman
2011-06-08 22:04 ` Mick
2011-06-09 1:25 ` Paul Hartman
2011-06-09 5:46 ` Mick
2011-06-09 15:06 ` Paul Hartman
2011-06-09 15:51 ` Paul Hartman
2011-06-09 20:27 ` Mick
2011-06-09 20:52 ` Paul Hartman
2011-06-09 11:16 ` Tanstaafl
2011-06-09 14:23 ` Mick
2011-06-09 16:21 ` Paul Hartman
2011-06-08 19:45 ` Paul Hartman
2011-06-08 20:08 ` Alan McKinnon [this message]
2011-06-08 20:01 ` Paul Hartman
2011-06-09 2:15 ` Dale
2011-06-09 3:23 ` Pandu Poluan
2011-06-09 4:50 ` Dale
2011-06-09 5:14 ` Paul Hartman
2011-06-09 6:52 ` Dale
2011-06-09 7:46 ` Alan McKinnon
2011-06-09 8:48 ` Dale
2011-06-10 15:46 ` Dale
2011-06-10 16:03 ` Paul Hartman
2011-06-10 17:39 ` Dale
-- strict thread matches above, loose matches on Subject: below --
2011-06-09 1:52 Pandu Poluan
2011-06-10 1:52 Pandu Poluan
2011-06-10 7:22 ` Joost Roeleveld
2011-06-10 10:08 ` Pandu Poluan
2011-06-10 13:17 ` Joost Roeleveld
2011-06-10 14:30 ` Alan McKinnon
2011-06-10 15:59 ` Joost Roeleveld
2011-06-10 16:04 ` Paul Hartman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201106082208.04183.alan.mckinnon@gmail.com \
--to=alan.mckinnon@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox