Issues with HTTPS records using Route53

Based on your description, there are a few potential issues with your HTTPS record configuration in Route 53:

1. DNS Propagation Delay: DNS changes can take 24-48 hours to propagate globally due to ISP caching. You may need to wait for this timeframe before testing again.

2. Name Server Configuration: Ensure that the NS records at your domain registrar exactly match the ones provided by AWS Route 53 for your hosted zone. Even a small discrepancy can prevent proper resolution.

3. Record Configuration: For HTTPS records, the format is important. Route 53 now supports HTTPS records which provide clients with improved performance and privacy by including additional connection information beyond just IP addresses.

4. Hosted Zone Type: Confirm you're using a Public Hosted Zone in Route 53, not a Private Hosted Zone, as this could explain why lookups are failing.

5. A Records: You might need to ensure you have proper A records set up in addition to the HTTPS records, as not all clients support HTTPS record types yet.

The DNS_PROBE_FINISHED_NXDOMAIN error suggests that the domain name cannot be resolved at all, which points to a fundamental DNS configuration issue rather than just an HTTPS record problem. This typically means either:

• The domain's NS records at the registrar don't match Route 53's name servers
• The hosted zone is not properly configured
• DNS propagation hasn't completed

I recommend verifying your domain's name server configuration and checking that all four name server records in the registered domain match the name server records in the hosted zone. You can use tools like 'dig' or 'whois' to check the current DNS configuration and verify propagation.
Sources
route53 problem | AWS re:Post
Domain Connection Issue: NXDOMAIN Error | AWS re:Post
Amazon Route 53 announces HTTPS, SSHFP, SVCB, and TLSA DNS resource record support - AWS

That advice above does not solve my issue, and I would really like to get this fixed.