Generated: 2022-07-24T00:00:01Z -- 2022-07-24T00:00:04Z

Disclaimer:

The following report was generated automatically. Packet loss and network issues may have introduced false positives. Please verify the results before taking action.
You can report issues with this report to: marka@isc.org

Why you should care:

Most recursive resolvers now support EDNS. Lack of EDNS support in authoritative servers results in additional queries being made as the recursive servers need to retry with plain DNS and results in slower DNS resolution.

Not answering EDNS queries is particularly bad as that is indistingishable from packet loss.

Incorrect EDNS behaviour when presented with unknown EDNS versions and EDNS options can result in DNS resolution failures and/or DNSSEC validation failures.

Failure to run fully EDNS compliant nameservers will make it hard to deploy developments like DNS COOKIES which provides mitigation against DNS amplification attacks, off path spoofing resistance, RRL advoidance and excessive resource usage.

Codes

ok - test passed.
badvers - BADVERS returned.
badversion - expected EDNS version not found.
echoed - EDNS option echoed back.
formerr - FORMERR returned.
mbz - EDNS flags echoed back.
nodo - EDNS DO flag not echoed.
noopt - OPT record not found when expected. nosoa - SOA not found when expected.
notimp - NOTIMP returned.
refused - REFUSED returned.
servfail - SERVFAIL returned.
soa - SOA found when not expected.
status - expected status code not found.
toobig - UDP response bigger that advertised buffer size.
version - expected EDNS version not found.
reset - TCP connection reset.
timeout - lookup timed out.