问题原文
原帖链接 · Old McStopher · CC BY-SA 3.0
I'm needing to register some domains that have country code domain extensions, but noticed that those TLDs do not officially support (A) IPv6 or (B) DNSSEC... What limitations or pitfalls should I expect to run into because of this?
(A) No IPv6 support for TLD
I know this means that I won't be able to add an AAAA record to the domain, but what does this mean for reachability/compatibility/visibility from other IPv6-capable DNS servers?
(B) No DNSSEC support for TLD
I understand that DNSSEC is somehow important for authenticating DNS resolving, but have no idea if/how its implementation (or lack thereof) affects me as an application developer when it comes to security.
NOTE: Please forgive this potentially rudimentary question from a spoiled LAMP, MEAN, front-end, and native mobile dev who's rarely had to make network architecture decisions pivoting around the above. Thanks in advance!
社区高分解答
原帖链接 · Calle Dybedahl · CC BY-SA 3.0
If the ccTLD does not have IPv6 addresses for its name servers, an IPv6-only user may not be able to resolve any names under that TLD, even if those names are in IPv6-competent zones. Resolving follows a chain down from root, and if one link doesn't work, the entire thing fails.
DNSSEC provides cryptographic authentication of DNS data. Like everything in DNS, it follows the normal tree starting at the root zone. And again, if one link doesn't work, the entire chain fails. So any names under a ccTLD that doesn't do DNSSEC will be vulnerable to spoofing (note: there is a technique for side-stepping the chain in this case, called DLV. It is, however, deprecated and ICANN's support for it will end in 2017).
I would consider using a better TLD :-)
摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。
