DNS
...
Integration Workflow
Before you start
6 min
verify your environment meets these requirements supported hardware {{k3}} , application version 6 3 1 3 or later supported operating systems linux required access an account on the kmes with administrator permissions to create roles, identities, tls pki, and update system settings local administrator/root access on all hosts where you install or configure components network and firewall outbound tcp/2001 from the bind server to the kmes series 3 fqdn or cidr (for example, kmes example com or 10 0 0 0/24 ) tls inspection or ssl proxies can break mutual tls handshakes exempt the kmes fqdn(s) from inspection configure the kmes series 3 with an fqdn so the exemption applies other openssl (version 3 0 0 or newer) bind (version 9 20 or newer) bind must be compiled from source to work with futurex hsms installing via package managers may cause linking issues between bind9 utils and openssl providers