IBM Cloud Docs
Why can't I create or delete a cross-account DNS resolution binding or delegated resolver type in a DNS-shared VPC?

Why can't I create or delete a cross-account DNS resolution binding or delegated resolver type in a DNS-shared VPC?

When you configure DNS sharing for Virtual Private Endpoint (VPE) gateways, you might encounter issues. Often, you can recover by following a few steps.

When creating or deleting a DNS resolution binding between a DNS-shared VPC and a cross-account DNS hub VPC, you receive a 401 unauthorized error. You recieve the same error when updating the DNS resolver type of a DNS-shared VPC to delegated.

If the hub and DNS-shared VPCs are in different accounts, IAM uses a delegation token to check if the service-to-service (s2s) authorization grants Read access on the hub VPC to the DNS-shared VPC. If IAM denies this action, a 401 unauthorized error message is returned.

If the DNS hub and DNS-shared VPCs are on different accounts, you must have an s2s authorization policy granting Read access on the hub VPC to the DNS-shared VPC. For more information, see Establishing service-to-service authorization.