the record type 35 on a dns server represents an ipv6 host.
the record type 35 on a dns server represents an ipv6 host.
which record type on a dns server represents an ipv6 host?
35
a device with dual-stack implementation in the operating system has an ipv4 and ipv6 address, and can communicate with other nodes in the lan or the internet using either ipv4 or ipv6. the domain name system (dns) protocol is used by both ip protocols to resolve fully qualified domain names (fqdn) and ip addresses, but dual stack requires that the resolving dns server can resolve both types of addresses. such a dual stack dns server would hold ipv4 addresses in the a records, and ipv6 addresses in the aaaa records. depending on the destination that is to be resolved, a dns name server may return an ipv4 or ipv6 ip address, or both. a default address selection mechanism, or preferred protocol, needs to be configured either on hosts or the dns server. the ietf has published happy eyeballs to assist dual stack applications, so that they can connect using both ipv4 and ipv6, but prefer an ipv6 connection if it is available. however, dual-stack also needs to be implemented on all routers between the host and the service for which the dns server has returned a ipv6 address. dual-stack clients should only be configured to prefer ipv6, if the network is able to forward ipv6 packets using the ipv6 versions of routing protocols. when dual stack networks protocols are in place the application layer can be migrated to ipv6.
ipv6
unlike 6to4, where the two halves of a connection can use different relays, traffic between a native ipv6 host and a teredo client uses the same teredo relay, namely the one closest to the native ipv6 host network-wise. the teredo client cannot localize a relay by itself (since it cannot send ipv6 packets by itself). if it needs to initiate a connection to a native ipv6 host, it sends the first packet through the teredo server, which sends a packet to the native ipv6 host using the client's teredo ipv6 address. the native ipv6 host then responds as usual to the client's teredo ipv6 address, which eventually causes the packet to find a teredo relay, which initiates a connection to the client (possibly using the teredo server for nat piercing). the teredo client and native ipv6 host then use the relay for communication as long as they need to. this design means that neither the teredo server nor client needs to know the ipv4 address of any teredo relays. they find a suitable one automatically via the global ipv6 routing table, since all teredo relays advertise the network 2001::/32.
teredo tunneling