Reaching the web site requires more than an ip6.arpa record.
It requires an AAAA record:
baikal:owen (68) ~ % host -t AAAA www.newnog.org 2011/02/07 13:51:23
www.newnog.org has no AAAA record
And it requires the host answer on port 80 at its IPv6 address, which
does appear to already be the case.
So, when I'm informed that the AAAA record is up, I'll retest.
Owen
[Reply-To: set to -futures@, as I don't think this is an operational issue.]
We all know that many people have no IPv6 connectivity. But I've only heard about future Internet-users without IPv4 connectivity... I didn't realize it was reality for Owen today.
(Even my IPv6 phone via T-Mobile has NAT64 connectivity to www.newnog.org.)
Cheers,
-Benson
Apologies to Mike,
It was not my intention to brow-beat him publicly. Indeed, I acknowledge
that he has the problem well in hand and is actively working on resolving
the issue.
My only intent was to point out to the person who claimed an ip6.arpa
record and a host which had an IPv6 address on its interface alone were
not a web site accessible on IPv6.
I fully expect the AAAA record to be placed soon and it looks like that
is the last remaining hurdle. Once that is done, I will pay my dues.
Owen
Owen DeLong <owen@delong.com> writes:
I fully expect the AAAA record to be placed soon and it looks like that
is the last remaining hurdle. Once that is done, I will pay my dues.
There have been AAAA records in the zone for ages. I don't have a
problem with you calling out our oversight on a public mailing list,
but failure to CC the email address in the SOA's RNAME loses you a bit
of best-practices high ground, don't you think?
rs@bifrost [13] % rcsdiff -c -r1.4 -r1.5 newnog.org.db