On 5 sep 2003, at 10.12, Jakob Schlyter wrote:
is there any operational considerations before putting both A and AAAA records on a name used glue? or, should one use separate names for v4 and v6 transport?
I personally would put A and AAAA for the same name. Otherwise I guess there is a risk the resolver using only IPv4 will query for A RR for ns1.ipv6.example.com, which of course will not exist. A and AAAA should use the same namespace. I think the same is true for any service which uses domain names when addressing services. One use in the example below ns1.example.com as the domain name for the nameserver for example.com, and that is true regardless of what transport you use. Similar rules should be true for HTTP, SMTP etc. paf
e.g.:
example.com. NS ns1.example.com. NS ns2.example.com. ns1.example.com. A 192.0.2.1 AAAA dead:beef::1 ns2.example.com. A 192.0.2.2 AAAA dead:beef::2 vs example.com. NS ns1.example.com. NS ns1.ipv6.example.com. NS ns2.example.com. NS ns2.ipv6.example.com. ns1.example.com. A 192.0.2.1 ns1.ipv6.example.com. AAAA dead:beef::1 ns2.example.com. A 192.0.2.2 ns2.ipv6.example.com. AAAA dead:beef::2
yours,
jakob