DNS64
E123433
DNS64 is a network mechanism that synthesizes IPv6 addresses from IPv4 DNS records to enable IPv6-only clients to reach IPv4-only servers, typically used together with NAT64.
All labels observed (2)
| Label | Occurrences |
|---|---|
| DNS64 canonical | 2 |
| DNS64: DNS extensions for Network Address Translation from IPv6 Clients to IPv4 Servers | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T1077175 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DNS64 Context triple: [NAT64, oftenUsedWith, DNS64]
-
A.
NAT64
NAT64 is a network address translation mechanism that enables IPv6-only clients to communicate with IPv4 servers by translating between the two protocol address spaces and packet formats.
-
B.
Teredo
Teredo is a tunneling protocol that enables IPv6 connectivity for devices on IPv4 networks, particularly those behind NAT.
-
C.
Internet Protocol version 6
Internet Protocol version 6 (IPv6) is the modern Internet addressing and routing protocol designed to replace IPv4 by providing a vastly larger address space and improved network efficiency and security features.
-
D.
DNS over QUIC (DoQ)
DNS over QUIC (DoQ) is a modern DNS transport protocol that uses the QUIC encrypted, multiplexed UDP-based transport to provide faster, more secure, and more reliable DNS queries than traditional methods.
-
E.
BGP-4+
BGP-4+ is an enhanced version of the Border Gateway Protocol designed to support routing for IPv6 networks.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: DNS64 Target entity description: DNS64 is a network mechanism that synthesizes IPv6 addresses from IPv4 DNS records to enable IPv6-only clients to reach IPv4-only servers, typically used together with NAT64.
-
A.
NAT64
NAT64 is a network address translation mechanism that enables IPv6-only clients to communicate with IPv4 servers by translating between the two protocol address spaces and packet formats.
-
B.
Teredo
Teredo is a tunneling protocol that enables IPv6 connectivity for devices on IPv4 networks, particularly those behind NAT.
-
C.
Internet Protocol version 6
Internet Protocol version 6 (IPv6) is the modern Internet addressing and routing protocol designed to replace IPv4 by providing a vastly larger address space and improved network efficiency and security features.
-
D.
DNS over QUIC (DoQ)
DNS over QUIC (DoQ) is a modern DNS transport protocol that uses the QUIC encrypted, multiplexed UDP-based transport to provide faster, more secure, and more reliable DNS queries than traditional methods.
-
E.
BGP-4+
BGP-4+ is an enhanced version of the Border Gateway Protocol designed to support routing for IPv6 networks.
- F. None of above. chosen
Statements (47)
| Predicate | Object |
|---|---|
| instanceOf |
DNS extension
ⓘ
IPv6 transition technology ⓘ network protocol mechanism ⓘ |
| advantage |
avoids dual-stack deployment on clients
ⓘ
centralizes translation at network edge ⓘ |
| canBe |
stateful at resolver level for logging or policy
ⓘ
stateless in address synthesis ⓘ |
| category |
DNS-based address translation helper
ⓘ
IPv4-to-IPv6 coexistence mechanism ⓘ |
| compatibleWith |
recursive DNS resolvers
ⓘ
stub resolvers on clients ⓘ |
| definedIn | RFC 6147 ⓘ |
| documentTitle |
DNS64
self-linksurface differs
ⓘ
surface form:
DNS64: DNS extensions for Network Address Translation from IPv6 Clients to IPv4 Servers
|
| firstPublishedYear | 2011 ⓘ |
| function |
construct synthetic AAAA responses
ⓘ
embed IPv4 address into IPv6 address ⓘ intercept AAAA queries ⓘ query A records when AAAA records are absent ⓘ |
| governingBody | Internet Engineering Task Force ⓘ |
| limitation |
depends on NAT64 for packet translation
ⓘ
does not translate traffic by itself ⓘ may affect DNSSEC validation if not handled carefully ⓘ may break applications using literal IPv4 addresses ⓘ |
| operatesOn |
A DNS records
ⓘ
AAAA DNS records ⓘ |
| operationalRole | runs on recursive DNS resolvers in the provider network ⓘ |
| prefixExample | 64:ff9b::/96 ⓘ |
| primaryPurpose | enable IPv6-only clients to reach IPv4-only servers ⓘ |
| relatedTo |
DNSSEC
ⓘ
IPv6 transition mechanisms ⓘ NAT64 ⓘ |
| reliesOn |
DNS resolver support
ⓘ
IPv6-only client configuration ⓘ |
| requires | NAT64 translator in the data path ⓘ |
| requiresConfiguration | DNS64 prefix on recursive resolver ⓘ |
| standardStatus | IETF Proposed Standard ⓘ |
| synthesizes | IPv6 addresses from IPv4 DNS records ⓘ |
| typicalDeployment |
IPv6-only access networks
ⓘ
carrier networks ⓘ enterprise networks ⓘ mobile networks ⓘ |
| usedWith |
IPv4-only servers
ⓘ
IPv6-only hosts ⓘ |
| uses |
network-specific NAT64 prefix
ⓘ
well-known NAT64 prefix ⓘ |
| usesStandard | Domain Name System ⓘ |
| worksTogetherWith | NAT64 ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: DNS64 Description of subject: DNS64 is a network mechanism that synthesizes IPv6 addresses from IPv4 DNS records to enable IPv6-only clients to reach IPv4-only servers, typically used together with NAT64.
Referenced by (3)
Full triples — surface form annotated when it differs from this entity's canonical label.
this entity surface form:
DNS64: DNS extensions for Network Address Translation from IPv6 Clients to IPv4 Servers