Route53 ZoneDelegationRecord doesn't accept PublicHostedZone hostedZoneNameServers

[skorfmann]

Given I have two zones, where I want to delegate from one zone to the other, I can't use the L2 Route53 ZoneDelegationRecord.

So, this issue appears to be, that hostedZoneNameServers returns null | string[] rather than just string[]. I tried this:

{
  zone: mainZone,
  delegatedZoneName: previewZone.zoneName,
  nameServers: <string[]>mainZone.hostedZoneNameServers
}

While this satisfies the type, it fails when actually running it via the CDK.

What I ended up doing for now:

const zoneDelegationResource = zoneDelegation.node.findChild(
  "Resource"
) as route53.CfnRecordSet;

zoneDelegationResource.addPropertyOverride(
  "ResourceRecords",
  mainZone.hostedZoneNameServers
);

[rix0rrr]

While this satisfies the type, it fails when actually running it via the CDK.

Could you give more details on this? Because it sure seems like that should work.

[RomainMuller]

@skorfmann as mentioned in the documentation the nameServers attribute is not available for private hosted zones and hosted zones that are imported from another stack.

In your particular case, you can assert the name servers are present by simply adding an exclamation mark:

const zoneDelegation = new route53.ZoneDelegationRecord(this, 'PreviewZoneDelegation', {
  zone: mainZone,
  delegatedZoneName: previewZone.zoneName,
  nameServers: previewZone.hostedZoneNameServers! // <-- the "!" means "I know this won't be undefined"
});

Also - note that I changed the nameServers property to be those of the previewZone, as the delegation record is created in the delegating zone and point to the delegated servers.

[RomainMuller]

I've tested this and it appears there is a bug related to how the tokens are handled here, which causes the code to crash with an obscure error. I am preparing a fix for this.

[RomainMuller]

#1853 includes a fix for the bug in question, and also introduces an API such that you could:

mainZone.delegateTo(previewZone);

[skorfmann]

In your particular case, you can assert the name servers are present by simply adding an exclamation mark:

Sweet, didn't know that.

#1853 includes a fix for the bug in question, and also introduces an API such that you could:

Awesome, thank you!