Differences between current version and previous revision of AAAAvsA6.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
| Newer page: | version 4 | Last edited on Sunday, November 28, 2004 11:43:39 am | by AristotlePagaltzis | |
| Older page: | version 3 | Last edited on Wednesday, November 24, 2004 4:56:22 pm | by MikeBeattie | Revert |
@@ -1,12 +1,17 @@
-For [IPv6] there are two types of [DNS] address format
, [
AAAA]
and [
A6]
.
+For [IPv6] there are two types of [DNS] ResourceRecord
, <tt>
AAAA</tt>
and <tt>
A6</tt>
.
-[
AAAA]
is the simple one -it works just like an [
A]
record in [IPv4], but with more bits.
+<tt>
AAAA</tt>
is the simple one -
- it works just like an <tt>
A</tt>
record in [IPv4], but with more bits.
-[
A6]
supports fragments of [IPv6] addresses. You can say "
example.com"
has the fragment "
2002:c000:0201"
, "
engineering.example.com"
has "the example.com fragment" + "
:0001"
, and "
foo.engineering.example.com"
has "the engineering prefix" + "
:0000:0000:0000:0001"
. This means that when example.com renumbers, they change one [DNS] record (
example.com)
and all of their machines have been renumbered.
+<tt>
A6</tt>
supports fragments of [IPv6] addresses. You can say <tt>
example.com</tt>
has the fragment <tt>
2002:c000:0201</tt>
, <tt>
engineering.example.com</tt>
has "the example.com fragment" + <tt>
:0001</tt>
, and <tt>
foo.engineering.example.com</tt>
has "the engineering prefix" + <tt>
:0000:0000:0000:0001</tt>
. This means that when <tt>
example.com</tt>
renumbers, they change just the
one ResourceRecord for <tt>
example.com</tt>
and all of their machines have been renumbered.
-Some people complain that [
A6]
is too complicated, and prone to problems (
What is the [TTL] on the response if the fragments all have different lifetimes?
What's the status of it if some of the entries (but not all of them) are signed with [DNSSEC]?
What protection is there against DoS?) The [A6] people say that it's necessary for networks that regularly change IP address (eg: networks that use a dynamic 6to4 address).
+Some people complain that <tt>
A6</tt>
is too complicated, and prone to problems:
+*
What is the [TTL] on the response if the fragments all have different lifetimes?
+*
What's the status of it if some of the entries (but not all of them) are signed with [DNSSEC]?
+*
What protection is there against [
DoS]
?
-[A6]
in general is the newer standard, and [
AAAA]
is the older standard, however, there doesn't yet appear to be much momentum for [
A6]
support.
+The <tt>A6</tt> people say that it's necessary for networks that regularly change
[IP] address (eg: networks that use a dynamic 6to4 address).
+
+<tt>
A6</tt>
in general is the newer standard, and <tt>
AAAA</tt>
is the older standard, however, there doesn't yet appear to be much momentum for <tt>
A6</tt>
support.
-----
CategoryDns
