"Resource Not Found" Error When Configuring Custom Email Domain in Okta

During custom email domain configuration, Okta generates a resource not found error if the required Domain Name System (DNS) records remain unreachable. Resolving this issue requires verifying the DNS records for accuracy, ensuring they are publicly visible, and allowing sufficient time for DNS propagation before re-initiating the verification process. The email sender creation process fails with the following error message:

Not found: Resource not found: <Domain> (Domain)

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Custom Email Domain
• DNS records
• Branding

During email domain configuration, Okta checks for the four required DNS records: one Text (TXT) record for domain verification and three Canonical Name (CNAME) records for routing, Sender Policy Framework (SPF), and DomainKeys Identified Mail (DKIM). This check is part of domain verification and the automatic generation of additional records. If the DNS records remain invisible or unreachable, the verification fails because Okta cannot validate domain ownership. Even if the DNS records exist, DNS-related issues, such as slow propagation or DNS server outages, make the records unreachable and cause this error.

How does an Okta Administrator resolve the "Not found: Resource not found" error during custom email domain configuration?

Verify the accuracy and public visibility of the generated DNS records, allow time for propagation, and re-initiate the domain verification process in the Admin Console.

1. Verify the exact spelling of the generated DNS records, ensuring there are no typographical errors in the hostnames or target values.
2. Confirm that no duplicate DNS records exist for the specified domain, as conflicting records prevent successful resolution.
3. Use a public DNS lookup tool (for example, nslookup or dig) to query the TXT and CNAME records from an external network to ensure they remain publicly visible.
4. Allow sufficient time for DNS propagation. Propagation takes up to 48 hours, depending on the domain's Time to Live (TTL) settings.
5. Investigate the DNS server configuration to ensure it responds to public queries and does not restrict access via firewall rules.
6. Return to the Admin Console and select Verify to re-initiate the domain verification process once the records resolve publicly.