By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Some resolutions fail for CloudFront distributions with custom domain names

0

In some cases (0.1%), my Unity application reports that a custom domain name can't be resolved. It happens for two CloudFront distributions with a custom domain, namely cdn.mogaland.io (front for S3) and api.mogaland.io (front for API Gateway).

In Route53, I have two alias records (A and AAAA) for each distribution. Each distribution is set with its custom domain and uses the same SSL certificate. I never received a report for a domain resolution failure for auth.mogaland.io (alias for Cognito).

What could be the root cause? What would be an effective resolution mechanism for the fatal issue?

Topics
Networking & Content Delivery
Tags
Amazon CloudFrontAmazon Route 53Domain Name System (DNS)
Language
English
Dom_D
asked a month ago134 views
1 Answer
0
Accepted Answer

Hello,

Please make sure to double-check the configuration of your DNS zone in Route53.

To investigate the resolution failures of your Route53 zone, you would need to provide more specific details about the error, as we don't have access to your environment/configuration.

Do you have any delegations in your zone? One common cause for intermittent NXDOMAIN errors are wrongly configured delegations. Delegations must always be created in the immediate parent zone, not in a grandparent zone.

I recommend to contact AWS Support, they are able to review your specific setup and provide more tailored guidance to resolve the issue. This is not an official support channel.

AWS
Roland
answered a month ago
  • Dom_D
    a month ago

    Thanks Roland.

    The error message I get from the network stack is just something like: Unexpected failure -- Could not resolve host 'cdn.mogaland.io'...

    Route53 is my actual registrar for the mogaland.io domain. There's no delegations for the corresponding zone, all subdomain records are defined in the top zone.

    Thanks for your feedback. I'm going to contact AWS Support now.

Relevant content