** Note that this is a public ticket, please refrain from adding any sensitive data. **

When FIPS is set the bind.config is automatically converted to add two algorithms to the disable-algorithms list. Those two are;

ED25519;
ED448;

With the FIPS policy active on a host with named running and governed by the global policy the rule will still hit for the host. A user can only see why when using the --diagnosis or --show-results insights-client options. Using that we see;

  },
  "details": {
   "bind": true,
   "type": "rule",
   "error_key": "NO_CPOL_BIND",
   "bind_noncompliant_algorithms": [
    "ED25519",
    "ED448"
   ],
   "bind_noncompliant_ds_digests": []
  }, 

We should update the rule so that it does not detect that these algorithms in the disabled list are in use.