DNS proxy guidelines

RFC 5625 - DNS Proxy Implementation Guidelines

Every requirement listed for RFC 5625, the tests linked to it, and their recorded reviews. This summary is included in the automatic compliance check, ./le rfc check.

Overview

Positive

what Ze has

Tested both ways4of 12 mandatory requirements

a positive test proves Ze does what the requirement demands and a negative one proves it refuses what the requirement forbids

One polarity plus reason8of 12 mandatory requirements

the requirement admits no counter-case, so one polarity plus a recorded reason is the whole proof available for it

One polarity, unexcused0of 12 mandatory requirements

one direction is tested, the other is neither tested nor excused, and nothing states which

Partial proof; remaining gap0of 12 mandatory requirements

scoped tests exist; the remaining obligation is unmet or unproven, with zero whole-requirement credit

Declared gap or no test0of 12 mandatory requirements

the requirements the summary declares a gap for, which say what Ze does not do yet, plus the ones no test carries and no annotation excuses. The at-a-glance table lists them apart: declared gaps (at every level), and mandatory requirements with no test and no annotation

Tests shown to detect a fault1616 of 16 tests linked to requirements

each test was observed to fail when the code it checks was deliberately broken. The test, its stated claim, and the relevant code are checked against the saved record for changes; the deliberate fault is not run again. Having both positive and negative tests counts as proof only after this check has demonstrated that they can detect a fault

Neutral

measures that are neither good news nor bad

Out of scope0of 12 mandatory requirements

an obligation that does not bind Ze, counted once its evidence passes. A {not-applicable} annotation says it never bound; a {feature-declined} annotation says its condition is an optional feature Ze does not offer, and quotes the RFC sentence that makes it optional. An annotation whose evidence fails is not counted here: the figures count it as exclusion unchecked. This classification records applicability and forms part of the total accounted for by the cards on this page

Not applicable0of 12 mandatory requirements

a {not-applicable} annotation says the obligation does not bind Ze. No test is owed only once its evidence passes; one whose evidence fails stays owed, and the figures count it as exclusion unchecked. It remains in the total that these cards add up to

Met below Ze0of 12 mandatory requirements

a {lower-layer} annotation says a layer under Ze performs the behavior, on state Ze installs into that layer, and names the producer that installs it. The obligation binds Ze and stays in the MUST bar, outside Ze proven: it is OS verified once a tagged test checks that layer's behavior on the state Ze installs, with a recorded break, and an OS testing gap until then

Optional feature declined0of 12 mandatory requirements

a {feature-declined} annotation says the obligation is conditional on a feature the RFC makes optional and Ze does not offer, and it quotes the sentence that makes it optional. The condition is false, so nothing is owed once that quote passes its evidence check; one whose quote fails stays owed, and the figures count it as exclusion unchecked. It remains in the total that these cards add up to

Linux cannot do this0of 12 mandatory requirements

Linux cannot provide the primitive this requirement needs. The obligation still binds Ze and stays unmet, but as a limit of the kernel, not of Ze's code: once its limit entry is verified, the row is not owed (OS blocked) and is left out of the MUST bar; one whose entry fails stays owed, and the figures count it as not built. It remains in the total that these cards add up to and earns no proof credit

Totals

what the cards above are counted against

Mandatory requirements (MUST level)12of 27 requirements this summary lists, at all levels

The RFC's MUST, MUST NOT, SHALL, SHALL NOT and REQUIRED requirements included in the automatic checks: the compliance check (./le rfc check) holds Ze to each of them. This is the total being assessed; the counts above show the recorded status of those requirements.

The 9 counts marked as a part above are the whole of the 12 mandatory requirements: they add up to 12. Tests shown to detect a fault counts individual tests rather than requirements, so its count is separate.

How to read the colors

A color names what the measure MEANS, not how well Ze scores on it. Green is a good outcome at any value, red is a bad one, and neither a population nor a scope count is an outcome, so both take no color. The number under the label is what says how far Ze has got. An outlined card with no colored edge, under Totals, is a total the other cards are counted against, not a measure.

CardTone hereWhy that color
Out of scope neutral no color: an obligation that never bound Ze is neither an achievement nor a failure, and counting it either way would be a claim
Tested both ways ok green at every value: a test pair is the outcome this gate exists to produce, and the count under the label is what says how far Ze has got
One polarity plus reason ok green at every value: where no counter-case exists, one polarity IS the complete answer, and a recorded reason is what the gate demands beside it
One polarity, unexcused ok green at zero, RED above it: half a proof with no reason for the other half
Partial proof; remaining gap ok green at zero, RED above it: a tested clause cannot prove the whole requirement
Declared gap or no test ok green at zero, RED above it: a binding obligation that nothing shows Ze meets is owed, whether or not a reason is stated
Not applicable neutral no color: an obligation that never bound Ze is neither an achievement nor a failure, and counting it either way would be a claim
Met below Ze neutral no color: an obligation met below Ze is neither a test Ze wrote nor work Ze owes, and the two green counts above are what says how much Ze proves itself
Optional feature declined neutral no color: an obligation whose condition Ze never meets is neither an achievement nor a failure. The absent FEATURE is disclosed on the RFC's own status row, as an implementation gap a later scope decision can revisit
Linux cannot do this neutral neutral at every value: an evidenced platform limit is neither a proof nor a scope exemption
Tests shown to detect a fault ok green at every value: these tests have been shown to detect a deliberate fault. This card counts individual tests separately, so its total cannot be added to the requirement counts above
Audit verdicts warn RED on the first weak, wrong or unimplemented verdict, amber while a verdict is no longer current or a mandatory requirement is unreviewed, green when every one is judged sound and current
Mandatory requirements (MUST level) outlined outlined, with no colored edge: it is the total the other cards are counted against, not a measure, and a larger one is neither good news nor bad

At a glance

FieldValue
Public row DNS proxy guidelines
Automatic checks Included
Requirements 27
Mandatory requirements (MUST level) 12
Not applicable, so out of scope 0
Declared gaps 0
Declared gaps a test demonstrates 0
Mandatory requirements with no test and no annotation 0
Nightly-only evidence 0
Test tags 18
Tests linked to requirements 16
Recorded audit verdicts 0
Fault test records 16
Summary rfc/short/rfc5625.md
Requirement table rfc/requirements/rfc5625.md
RFC text rfc/full/rfc5625.txt

Automatic checks

Included in automatic checks: Summary written 2026-11-08 for spec-home-cpe-23 (owner decision D-2: RFC 5625 is followed and listed for fttx-edge). Walked forward and reverse in rfc/extraction/rfc5625.json on 2026-11-08: twelve MUST-level sites map the twelve gated rows, two are excluded (a description of RFC 1035, a quotation of RFC 3597)

Published support status

Area: DNS proxy guidelines

Proof: 12 of 12 MUST proven

Evidence: unit 12

Unmet: -

Coverage

BucketCountWhat it counts
Positive and negative tests 4 one part of the mandatory requirements
Annotated (including scoped evidence) 8 one part of the mandatory requirements
Only a positive or negative test 0 one part of the mandatory requirements
No test and no annotation 0 one part of the mandatory requirements
Partial proof; remaining gap (subset of annotated; zero whole-requirement credit) 0 also counted in one of the groups above
Evidence that runs nightly only 0 also counted in one of the groups above
Derived from other rows 0 excluded from the total: each summarizes the status of other requirements, which are already counted above
Mandatory requirements (MUST level)12every mandatory requirement appears in exactly one group above

Positive and negative tests (4): RFC5625-4.4-1, RFC5625-4.4-2, RFC5625-4.4-3, RFC5625-5.2-1

Annotated (including scoped evidence) (8): RFC5625-4.1-1, RFC5625-4.2-1, RFC5625-4.3-1, RFC5625-4.3-2, RFC5625-4.4.1-1, RFC5625-4.4.2-1, RFC5625-4.5-1, RFC5625-4.5-2

Figures

MUST bar

Ze proven 12

Overview bar

Ze MUST proven 12, Not assessed 15
FigureRows
RFCs 1
Requirements not reviewed 0
Mandatory requirements complete complete
MUST rows 12
MUST rows kept (the MUST bar) 12
Ze proven 12
OS verified 0
Proof pending 0
OS testing gap 0
Exclusion unchecked 0
Not assessed 0
Not built 0
MUST rows not owed 0
MUST not owed: feature-declined 0
MUST not owed: linux-limit 0
MUST not owed: not-applicable 0
SHOULD / MAY rows 15
SHOULD proven 0
SHOULD OS verified 0
SHOULD OS testing gap 0
SHOULD not owed 0
SHOULD not owed: feature-declined 0
SHOULD not owed: linux-limit 0
SHOULD not owed: not-applicable 0
SHOULD proof pending 0
SHOULD exclusion unchecked 0
SHOULD not assessed 15
SHOULD not built 0

The MUST bar shows mandatory requirements (MUST, MUST NOT, REQUIRED, SHALL and SHALL NOT) that Ze and its operating system must meet. It includes only RFCs whose requirement lists have been checked against the original text. Ze proven means a test has been shown to fail when the required behavior is deliberately broken. Behavior provided by the operating system or a library is OS verified when a test checks it using the settings Ze installs and has also been shown to detect a deliberate fault; until then, it is an OS testing gap. Proof pending counts requirements a tagged test covers that no deliberate fault has yet been shown to break and that nothing records as unmet. Exclusion unchecked counts requirements claimed not to apply to Ze whose evidence is still to be checked. Not assessed counts requirements no tagged test covers and that nothing records as unmet, so nothing yet says whether Ze meets them. Not built counts requirements the RFC summary or a test review says Ze does not meet, in full or in part. The overview bar adds optional requirements (MAY, NOT RECOMMENDED, OPTIONAL, RECOMMENDED, SHOULD and SHOULD NOT) and requirements that do not apply to Ze. An RFC marked requirements not reviewed is excluded from these figures because its requirement list has not been checked against the original text. Counts are loaded from the RFC data files.

Requirements

RequirementLevelSectionTests
RFC5625-4.1-1Therefore, proxies MUST ignore any unknown DNS flags and proxy those packets as usual. (§4.1)
MUST 4.1
negativeno testno negative test

{single-polarity}: the obligation is to proxy a packet whatever its flags, so no flag value exists that a conformant proxy refuses; a refusal is the violation the positive test catches

RFC5625-4.2-1Proxies MUST forward packets regardless of the presence or absence of compressed labels therein. (§4.2)
MUST 4.2
negativeno testno negative test

{single-polarity}: compressed and uncompressed packets are both forwarded, so no input exists that a conformant proxy refuses

RFC5625-4.3-1All requests and responses MUST be proxied regardless of the values of the QTYPE and QCLASS fields. (§4.3)
MUST 4.3
negativeno testno negative test

{single-polarity}: every QTYPE and QCLASS is proxied, so no question exists that a conformant proxy refuses

RFC5625-4.3-2Similarly, all responses MUST be proxied regardless of the values of the TYPE and CLASS fields of any Resource Record therein. (§4.3)
MUST 4.3
negativeno testno negative test

{single-polarity}: every TYPE and CLASS in a response is proxied, so no record exists that a conformant proxy withholds

RFC5625-4.4-1Where the required portions of a response would not fit inside that limit, the DNS server MUST set the "TrunCation" (TC) bit in the DNS response header to indicate that truncation has occurred. (§4.4)
MUST 4.4
RFC5625-4.4-2If a proxy must unilaterally truncate a response, then the proxy MUST set the TC bit. (§4.4)
MUST 4.4
RFC5625-4.4-3Similarly, proxies MUST NOT remove the TC bit from responses. (§4.4)
MUST NOT 4.4
RFC5625-4.4.1-1DNS proxies MUST therefore be prepared to receive and forward queries over TCP. (§4.4.1)
MUST 4.4.1
positiveunit/verifyTestRFC5625ProxyTCPAndOPT
negativeno testno negative test

{single-polarity}: every TCP query is received and forwarded, so no TCP query exists that a conformant proxy refuses

RFC5625-4.4.2-1As per Section 4.1, proxies MUST NOT refuse to proxy such packets. (§4.4.2)
MUST NOT 4.4.2
positiveunit/verifyTestRFC5625ProxyTCPAndOPT
negativeno testno negative test

{single-polarity}: the obligation is never to refuse a packet carrying an OPT RR, so its only test is that one is answered

RFC5625-4.5-1DNS proxies MUST implement Section 4.7 of [RFC2845] and either forward packets unchanged (as recommended above) or fully implement TSIG. (§4.5)
MUST 4.5
negativeno testno negative test

{single-polarity}: the obligation is to forward a signed query unchanged, so any change to it is the violation and no signed query exists that a conformant proxy may alter

RFC5625-4.5-2As per Section 4.3, DNS proxies MUST be capable of proxying packets containing TKEY [RFC2930] Resource Records. (§4.5)
MUST 4.5
positiveunit/verifyTestRFC5625TKEYQueryProxied
negativeno testno negative test

{single-polarity}: every packet carrying a TKEY RR is proxied, so no such packet exists that a conformant proxy refuses

RFC5625-5.2-1this option MUST NOT be sent to clients when no value is configured. (§5.2)
MUST NOT 5.2
RFC5625-3-1It is RECOMMENDED that proxies should be as transparent as possible, such that any "hop-by-hop" mechanisms or newly introduced protocol extensions operate as if the proxy were not there. (§3)
RECOMMENDED 3
positiveno testno positive test
negativeno testno negative test
RFC5625-3-2Except when required to enforce an active security or network policy (such as maintaining a pre-authentication "walled garden"), end-users SHOULD be able to send their DNS queries to specified upstream resolvers, thereby bypassing the proxy altogether. (§3)
SHOULD 3
positiveno testno positive test
negativeno testno negative test
RFC5625-3-3In this case, the gateway SHOULD NOT modify the DNS request or response packets in any way. (§3)
SHOULD NOT 3
positiveno testno positive test
negativeno testno negative test
RFC5625-4.4-4Since UDP packets larger than 512 octets are now expected in normal operation, proxies SHOULD NOT truncate UDP packets that exceed that size. (§4.4)
SHOULD NOT 4.4
positiveno testno positive test
negativeno testno negative test
RFC5625-4.4.1-2Therefore, whenever a proxy receives a request over TCP, the proxy SHOULD forward the query over TCP (§4.4.1)
SHOULD 4.4.1
positiveno testno positive test
negativeno testno negative test
RFC5625-4.4.1-3and SHOULD NOT attempt the same query over UDP first. (§4.4.1)
SHOULD NOT 4.4.1
positiveno testno positive test
negativeno testno negative test
RFC5625-4.4.3-1Therefore (irrespective of which of the above methods is in use), proxies SHOULD be capable of forwarding UDP packets up to a payload size of at least 4096 octets. (§4.4.3)
SHOULD 4.4.3
positiveno testno positive test
negativeno testno negative test
RFC5625-5.1-1As per Section 3, end-users SHOULD be able to send their DNS queries directly to specified upstream resolvers, ideally without hard-coding those settings in their stub resolver. (§5.1)
SHOULD 5.1
positiveno testno positive test
negativeno testno negative test
RFC5625-5.1-2It is therefore RECOMMENDED that gateways SHOULD support device- administrator configuration of values for the "Domain Name Server" DHCP option. (§5.1)
RECOMMENDED 5.1
positiveno testno positive test
negativeno testno negative test
RFC5625-5.2-2Since no standard exists for a "local" scoped domain name suffix, it is RECOMMENDED that the default value for this option SHOULD be empty (§5.2)
RECOMMENDED 5.2
positiveno testno positive test
negativeno testno negative test
RFC5625-6.1-1It is strongly RECOMMENDED that DNS proxies follow the relevant recommendations in [RFC5452], particularly those in Section 9.2 relating to randomisation of Query IDs and source ports. (§6.1)
RECOMMENDED 6.1
positiveno testno positive test
negativeno testno negative test
RFC5625-6.1-2If a DNS proxy is running on a broadband gateway with NAT that is compliant with [RFC4787], then it SHOULD also follow the recommendations in Section 10 of [RFC5452] concerning how long DNS state is kept. (§6.1)
SHOULD 6.1
positiveno testno positive test
negativeno testno negative test
RFC5625-6.2-1The DNS proxy in a gateway SHOULD NOT, by default, be accessible from the WAN interfaces of the device. (§6.2)
SHOULD NOT 6.2
positiveno testno positive test
negativeno testno negative test
RFC5625-6.3-2In these circumstances, proxies SHOULD synthesise a suitable DNS error response to the client (i.e., SERVFAIL) instead of dropping the packet completely. (§6.3)
SHOULD 6.3
positiveno testno positive test
negativeno testno negative test
RFC5625-6.3-1Examples of malformed packets that MAY be dropped include: (§6.3)
MAY 6.3
positiveno testno positive test
negativeno testno negative test

Gaps and untested MUSTs

RFC 5625 lists no missing behavior, and every mandatory requirement included in automatic checks has a linked test.

Proof state

A test reads unproven when no record shows it failing after a deliberate fault. Until then, its claim to check the requirement remains unproven.

RFC5625-4.1-1

Therefore, proxies MUST ignore any unknown DNS flags and proxy those packets as usual. (§4.1)

Audit verdict: not reviewed: no reviewer has checked whether these tests enforce the requirement

PolarityTestKind and tierProof state
positive TestRFC5625ResolverUnknownFlags unit/verify mutant, verified

RFC5625-4.2-1

Proxies MUST forward packets regardless of the presence or absence of compressed labels therein. (§4.2)

Audit verdict: not reviewed: no reviewer has checked whether these tests enforce the requirement

PolarityTestKind and tierProof state
positive TestRFC5625ResolverCompressedReply unit/verify mutant, verified

RFC5625-4.3-1

All requests and responses MUST be proxied regardless of the values of the QTYPE and QCLASS fields. (§4.3)

Audit verdict: not reviewed: no reviewer has checked whether these tests enforce the requirement

PolarityTestKind and tierProof state
positive TestRFC5625ResolverUnknownTypeAndClass unit/verify mutant, verified

RFC5625-4.3-2

Similarly, all responses MUST be proxied regardless of the values of the TYPE and CLASS fields of any Resource Record therein. (§4.3)

Audit verdict: not reviewed: no reviewer has checked whether these tests enforce the requirement

PolarityTestKind and tierProof state
positive TestRFC5625ResolverUnknownTypeAndClass unit/verify mutant, verified

RFC5625-4.4-1

Where the required portions of a response would not fit inside that limit, the DNS server MUST set the "TrunCation" (TC) bit in the DNS response header to indicate that truncation has occurred. (§4.4)

Audit verdict: not reviewed: no reviewer has checked whether these tests enforce the requirement

PolarityTestKind and tierProof state
negative TestRFC5625ResolverTruncationSetsTC unit/verify mutant, verified
positive TestRFC5625ResolverTruncationSetsTC unit/verify mutant, verified

RFC5625-4.4-2

If a proxy must unilaterally truncate a response, then the proxy MUST set the TC bit. (§4.4)

Audit verdict: not reviewed: no reviewer has checked whether these tests enforce the requirement

PolarityTestKind and tierProof state
negative TestRFC5625ResolverTruncationSetsTC unit/verify mutant, verified
positive TestRFC5625ResolverTruncationSetsTC unit/verify mutant, verified

RFC5625-4.4-3

Similarly, proxies MUST NOT remove the TC bit from responses. (§4.4)

Audit verdict: not reviewed: no reviewer has checked whether these tests enforce the requirement

PolarityTestKind and tierProof state
negative TestRFC5625ResolverNeverDropsTC unit/verify mutant, verified
positive TestRFC5625ResolverNeverDropsTC unit/verify mutant, verified

RFC5625-4.4.1-1

DNS proxies MUST therefore be prepared to receive and forward queries over TCP. (§4.4.1)

Audit verdict: not reviewed: no reviewer has checked whether these tests enforce the requirement

PolarityTestKind and tierProof state
positive TestRFC5625ProxyTCPAndOPT unit/verify mutant, verified

RFC5625-4.4.2-1

As per Section 4.1, proxies MUST NOT refuse to proxy such packets. (§4.4.2)

Audit verdict: not reviewed: no reviewer has checked whether these tests enforce the requirement

PolarityTestKind and tierProof state
positive TestRFC5625ProxyTCPAndOPT unit/verify mutant, verified

RFC5625-4.5-1

DNS proxies MUST implement Section 4.7 of [RFC2845] and either forward packets unchanged (as recommended above) or fully implement TSIG. (§4.5)

Audit verdict: not reviewed: no reviewer has checked whether these tests enforce the requirement

PolarityTestKind and tierProof state
positive TestRFC5625SignedQueryForwardedUnchanged unit/verify mutant, verified

RFC5625-4.5-2

As per Section 4.3, DNS proxies MUST be capable of proxying packets containing TKEY [RFC2930] Resource Records. (§4.5)

Audit verdict: not reviewed: no reviewer has checked whether these tests enforce the requirement

PolarityTestKind and tierProof state
positive TestRFC5625TKEYQueryProxied unit/verify mutant, verified

RFC5625-5.2-1

this option MUST NOT be sent to clients when no value is configured. (§5.2)

Audit verdict: not reviewed: no reviewer has checked whether these tests enforce the requirement

PolarityTestKind and tierProof state
negative TestOption15AbsentWhenUnconfigured unit/verify mutant, verified
positive TestOption15AbsentWhenUnconfigured unit/verify mutant, verified

Requirement list review

FieldValue
Reviewer ze-implement agent, spec-home-cpe-23 phase 3, 2026-11-08
Signed off 2026-11-08
Register rfc2119
Source rfc/full/rfc5625.txt
Source fingerprint d76369d28c5ab28d
Record rfc/extraction/rfc5625.json
Mapped sentences 12
Declined as scope 2
Relocated to a spec, which Ze OWES 0
Unclassified 0

Sections

SectionNameSitesDispositionReason
front not stated 0 skipped (front-matter) Header, status of this memo, copyright notice, abstract and table of contents.
1 not stated 0 reviewed not stated
2 not stated 0 reviewed not stated
3 not stated 0 reviewed not stated
4 not stated 0 reviewed not stated
4.1 not stated 2 reviewed not stated
4.2 not stated 1 reviewed not stated
4.3 not stated 3 reviewed not stated
4.4 not stated 3 reviewed not stated
4.4.1 not stated 1 reviewed not stated
4.4.2 not stated 1 reviewed not stated
4.4.3 not stated 0 reviewed not stated
4.5 not stated 2 reviewed not stated
5 not stated 0 reviewed not stated
5.1 not stated 0 reviewed not stated
5.2 not stated 1 reviewed not stated
5.3 not stated 0 reviewed not stated
6 not stated 0 reviewed not stated
6.1 not stated 0 reviewed not stated
6.2 not stated 0 reviewed not stated
6.3 not stated 0 reviewed not stated
7 Acknowledgements 0 skipped (acknowledgements) Acknowledgements.
8 References heading 0 skipped (references) References heading.
8.1 Normative references 0 skipped (references) Normative references.
8.2 Informative references 0 skipped (references) Informative references.

Excluded sentences

SiteExcluded kindReasonQuote
4.1:1 not-a-requirement
never bound Ze
the sentence states a fact or describes another document, and directs no implementation
Section 4.1 explains why proxies drop packets: it describes what RFC 1035 originally specified for the Z bits ("This may be because [RFC1035] originally specified"), and directs no proxy. The obligation it motivates is the next sentence, RFC5625-4.1-1. This may be because [RFC1035] originally specified that these unused "Z" flag bits "MUST" be zero.
4.3:1 cross-document
never bound Ze
the obligation belongs to another document that this one only cites
Section 4.3 quotes RFC 3597 ("[RFC3597] requires that resolvers MUST handle Resource Records (RRs) of unknown type transparently."); the obligation belongs to RFC 3597. The proxy obligation this document states is the next two sentences, RFC5625-4.3-1 and RFC5625-4.3-2. [RFC3597] requires that resolvers MUST handle Resource Records (RRs) of unknown type transparently.

Superseded

No document obsoletes RFC 5625, so its obligations are stated where they were written.