EDNS Compliance Tester

Checking: 'uaenorth.azure.glb.confluent.cloud' as at 2023-12-01T22:54:13Z

uaenorth.azure.glb.confluent.cloud. @ (glbns1.confluent.cloud.): dns=ok zflag=ok edns=ok edns1=ok edns@512=extra,notc ednsopt=ok edns1opt=ok do=ok ednsflags=ok docookie=ok edns512tcp=extra optlist=expire-bad

The Following Tests Failed

Warning: test failures may indicate that some DNS clients cannot resolve the zone or will get a unintended answer or resolution will be slower than necessary.

Warning: failure to address issues identified here may make future DNS extensions that you want to use ineffective. In particular echoing back unknown EDNS options and unknown EDNS flags will break future signaling between DNS client and DNS server. We already have examples of this where you cannot depend on the AD flag bit meaning anything in replies because too many DNS servers just echo it back. Similarly the EDNS Client Subnet (ECS) option cannot just be sent to everyone in part because of servers just echoing it back.


To retrieve this report in the future: https://ednscomp.isc.org/ednscomp/36090ff4e7

The source code for the tester can be downloaded from ISC Open Source Projects / DNS-Compliance-Testing.

For more information about EDNS please see the main site.

(IPv4 or IPv6)

© 2015 Internet Systems Consortium - Powered By: CGIC (License) - Thomas Boutell