Δαφνη Ευτυχια Αρθουρος

Huh. I just dumped my name server cache to peek at it, and found a bunch of IPv6 addresses in it. I'd glanced at some IPv6 info a while back and had been meaning to learn more and start playing with it, but back-burnered that project -- as far as I know, none of my computers are actually using it for anything yet (but at least a few are capable of it), and I'm not sure whether my firewall is one of the machines that knows IPv6 or whether my ISP routes it.[*] So while I may be mistaken, my guess is that the IPv6 entries in the cache were just part of routine responses by other name servers to queries originating on my LAN.

It doesn't mean anything until I do get around to learning how to set things up to make use of it beyond just verifying that 'ping6' runs on some of my machines (unless I'm wrong about how it got there and my web browser has been quietly using IPv6 without my realizing it, which I doubt), but I just found it kind of surprising, and also kind of nifty, that it's showing up.

I'm sure those of you who do know more about IPv6 than just the address syntax won't be surprised at all. But until this morning I had no idea that my name server was already seeing IPv6 information from the outside world.

[*] But I guess I can find out as soon as I finish typing this, by trying to ping6 one of the addresses I found in the cache. ... ... "socket: Address family not supported by protocol" -- I'll sort out what that means when I'm more awake.

"This mail is a test.
It is only a test.
If it were a real mail, it would be better word word-
ed, would start with a hail, contain words that allured.
So it's just for the best.
That this mail be a test."
        -- mnemex, 2007-01-03