DNS
...
Integration steps
Before you start
6 min
verify your environment meets these requirements supported hardware {{vectera}} , 7 2 x x or later supported operating systems linux required access an account on the {{vectera}} with administrator permissions to create application partitions, identities, tls pki, and update system settings local administrator/root privileges on the computer where bind is installed network and firewall allow outbound tcp port 9100 (default excrypt port) from the computer running bind to the {{vectera}} , specified by fqdn (for example, hsm example com ) or cidr (for example, 10 0 0 0/24 ) tls inspection or ssl proxies can break mutual tls handshakes exempt the {{vectera}} fqdn(s) from inspection configure the vectera plus with a fqdn so the exemption applies other openssl (v3 0 0 or newer) bind (v9 20 or newer) you must compile bind from source to work with {{futurex}} hsms using package managers to install bind might cause linking issues between bind9 utils and openssl providers