.\" Generated by Mmark Markdown Processor - mmark.miek.nl
.TH "COREDNS-SIIT" 7 "August 2026" "CoreDNS" "CoreDNS Plugins"

.SH "NAME"
.PP
\fIsiit\fP \- enables AAAA\->A translation support for DNS records based on SIIT (IPv6\->IPv4 translation).

.SH "DESCRIPTION"
.PP
The \fIsiit\fP plugin will when asked for a domain's A record,
synthesizes it from a corresponding AAAA record if it belongs to a certain IP range.

.PP
It also supports arbitrary mapping IPv6\->IPv4.

.PP
It is useful when published services are IPv6\-only and emit their AAAA record accordingly
but IPv4 clients reach them through a siit routing. This plugin generates the associated A records
for these clients automatically.

.SH "SYNTAX"
.PP
.RS

.nf
siit {
    ipv6\_prefix IPV6PREFIX
    eam IPV4 IPV6
}

.fi
.RE

.IP \(bu 4
\fB\fCipv6_prefix\fR specifies any local IPv6 prefix to use, instead of the well known prefix (64:ff9b::/96)
.IP \(bu 4
\fB\fCeam\fR translates the ipv6 to the corresponding ipv4, it can be set multiple times


.SH "EXAMPLES"
.PP
.RS

.nf
\&. {
    siit {
        ipv6\_prefix 64:1337::/96
    }
}

.fi
.RE

.SH "METRICS"
.PP
If monitoring is enabled (via the \fIprometheus\fP plugin) then the following metrics are exported:

.IP \(bu 4
\fB\fCcoredns_siit_requests_translated_total{server}\fR \- counter of DNS requests translated


.PP
The \fB\fCserver\fR label is explained in the \fIprometheus\fP plugin documentation.

.SH "BUGS"
.IP \(bu 4
Prefix matching in eam is not implemented yet.
.IP \(bu 4
DNSSEC support is not implemented yet. The problem is the same as DNS64. See: RFC 6147 Section 3
\[la]https://tools.ietf.org/html/rfc6147#section-3\[ra]


.SH "SEE ALSO"
.PP
See RFC 6052
\[la]https://tools.ietf.org/html/rfc6052\[ra] for more information on the SIIT mechanism
and RFC 7757
\[la]https://tools.ietf.org/html/rfc7757\[ra] about the explicit address mappings (eam) mechanism

.SH "NOTES"
.PP
This plugin is heavily based on dns64 plugin
\[la]../dns64\[ra].