Amazon Route 53 hosted zone is not configured correctly

Hi Jack,

The error message you're receiving indicates that your Route 53 hosted zone is not set as the authoritative DNS service for your domain. Since you mentioned your domain is registered with AWS, the most likely issue is a mismatch between the name servers configured at the domain registrar level and the name servers assigned to your Route 53 hosted zone.

Here's what you should verify:

First, check your registrar-level name servers by running the whois command for your domain. Then, compare these with the name servers listed in your Route 53 hosted zone (you can find these in the Route 53 console under your hosted zone details). These two sets of name servers must match exactly for your hosted zone to be authoritative.

If you find that the name servers don't match, you need to update your domain registration to use the name servers from your hosted zone. Even though your domain is registered with AWS, you still need to explicitly configure the domain registration to point to the correct name servers. You can do this through the Route 53 console by navigating to Registered Domains, selecting your domain, and editing the name servers to match those in your hosted zone.

When you recreated your hosted zone, Route 53 would have assigned a new set of name servers to it. If you didn't update your domain registration with these new name servers, that would explain why you're still experiencing the issue.

After updating the name servers at the domain registration level, DNS propagation can take up to 48 hours, though it's often much faster. Once the name servers match and propagate, your hosted zone will be authoritative and WorkMail should recognize the configuration as correct.
Sources
Troubleshoot DNS resolution issues for records in Route 53 public hosted zones | AWS re:Post
Adding or changing name servers and glue records for a domain - Amazon Route 53