Route53 hosted zone not seen as authoritative by Workmail even though NS records and SOA are correct

60 Views Asked by At

I am trying to add my domain (currentvoices.com) to the domain list in Workmail. I have copied the required records shown in Workmail using the copy button, and added them to the DNS record in Route53 for the public hosted zone.

I verified that the changes to the hosted domain are in sync, using the status link.

Workmail keeps saying the hosted zone is not configured correctly, that the domain needs to be set as authoritative.

I have deleted and recreated the hosted zone in Route53 multiple times, trying to resolve this issue. Unfortunately in Route53, I neglected to write down the original NS records prior to deleting and recreating the hosted domain.

Route53 creates new (different) NS records every time I recreate the hosted zone. It also creates an SOA record that points to one of the newly-created NS records.

Still the same message appears in Workmail, even if I remove and re-add the domain there.

Important: This domain has only ever been hosted on AWS Route53. Nowhere else. So it is not being managed anywhere else - that is not the problem.

I would very much appreciate any help. I'm thinking the problem may stem from not being able to update the NS records to the original ones. How can I resolve this?

Cheers, -=Cameron

I have tried:

  • Removing and recreating the public hosted domain in Route53
  • Deleting and re-adding the domain to the Domains list in Workmail
  • I also made sure the set of records specified by Workmail are correct to what's in the Route53 hosted domain record, in every case.
0

There are 0 best solutions below