We are using an externally registered domain (
niftygateway.com in AWS Route53) for our Netlify site
In AWS Route53, we have an A record set up on our apex record
niftygateway.com, which points to a cloudfront distribution. The cloudfront distribution has an origin set up pointing to our Netlify site at
giftynateway.netlify.app. This is working properly and users get directed to
giftynateway.netlify.app when accessing
We want to remove the cloudfront distribution by reconfiguring our A record in Route53 to point to the Nifty apex loadbalancer (
126.96.36.199), as described in these docs, Configure external DNS for a custom domain | Netlify Docs. However, Netlify documentation states “it may take up to a few hours for record changes to propagate”, and we do not want to interrupt traffic to our site while this propagation is happening.
We would like to test that this change will work by using one of the NETLIFY DNS records generated by Netlify; i.e.
netlify.niftygateway.com. We have attempted to create an A record in AWS Route53 for
netlify.niftygateway.com which points to the apex loadbalancer (
188.8.131.52). Whenever we attempt to access
netlify.niftygateway.com though, we receive an invalid certificate error.
Is our SSL certificate potentially not extended on this subdomain?
Is our testing methodology valid?
Any help is appreciated and please let us know if you need further information.