Minimal DNS64 relay, meant to sit between the DNS server of an IPv6 network, and the one of a (typically NAT64'ed) IPv4 one.
- Rust 100%
| Filename | Latest commit message | Latest commit date |
|---|---|---|
| src | ||
| .gitignore | ||
| Cargo.lock | ||
| Cargo.toml | ||
| dns64-relay.service | ||
| LICENSE | ||
| README.md | ||
DNS64 Relay
Minimal DNS64 relay, meant to sit between the DNS server of an IPv6 network, and the one of a (typically NAT64'ed) IPv4 one.
This program was made to provide a simple and very small solution to the following situation:
- let ASA be your own IPv6-capable network
- let ASB & ASC be IPv4-only networks occupying overlapping (or outright identical) IP ranges e.g. X.0.0.0/8.
- You can allow traffic from ASA to route to both ASB and ASC simultaneously by setting up NAT64 with distinct prefixes
- In the best of cases, domain names served by ASB and ASC already share a common suffix; e.g.
example.asb.net.vs.example.asc.net., so the DNS server for ASA can determine which of ASB or ASC's DNS server to interrogate for a given domain. - let the DNS server for ASA not support DNS64 (e.g. dnsmasq)
- How do you insert DNS64 translation into this? two instances of dns64-relay! Ideally colocated with their NAT64 equivalents.
Note that this also helps if ASA is IPv4-capable as well and shares the same IP range; all connections from ASA with ASB or ASC will simply be limited to IPv6, while IPv4 traffic in ASA will not escape.
Build
This software is written in Rust and builds with Cargo:
$ cargo build --release
target/release/dns64-relay
Deploy
dns64-relay can be deployed rather simply as a systemd service using the provided dns64-relay.service unit file.