| 1 |
Apparently, though unproven, at 21:45 on Wednesday 08 June 2011, Paul Hartman |
| 2 |
did opine thusly: |
| 3 |
|
| 4 |
> On Tue, Jun 7, 2011 at 8:27 PM, Dale <rdalek1967@×××××.com> wrote: |
| 5 |
> > Funny thing is, I use googles DNS servers. 8.8.8.8 and 8.8.4.4 are the |
| 6 |
> > settings. I find it ironic that Google is one of the ones hosting this |
| 7 |
> > event and it appears their server is not ready. Makes me think. < Dale |
| 8 |
> > scratches chin a bit > |
| 9 |
> |
| 10 |
> From Google DNS FAQ: |
| 11 |
> |
| 12 |
> Does Google Public DNS support IPv6? |
| 13 |
> Google Public DNS can respond to requests for IPv6 addresses (AAAA |
| 14 |
> requests), but it does not yet support native IPv6 transport and |
| 15 |
> cannot talk to IPv6-only authoritative nameservers. Clients should use |
| 16 |
> IPv4 network connections to use Google Public DNS. |
| 17 |
|
| 18 |
Almost all large auth servers out there are in exactly that position. Mine |
| 19 |
certainly are. Cisco are waiting in the wings with a gigantic[1] quote for |
| 20 |
what it will take to change that. |
| 21 |
|
| 22 |
[1] When I say "gigantic" I really do mean "gigantic", as in "OMFG, does the |
| 23 |
number of $US fit into the money field in Oracle Financials??". Not "gigantic" |
| 24 |
as in "oh, that's big, bigger than what we normally call big". |
| 25 |
|
| 26 |
Just wanted to add some perspective... |
| 27 |
|
| 28 |
-- |
| 29 |
alan dot mckinnon at gmail dot com |
Archives