- Newest
- Most votes
- Most comments
Hello Prashanth,
Thank you for contacting AWS Customer Support regarding enabling custom domains for your Cognito User pool. From the details provided, we gather that you have setup the custom domain - "https://oauth.vismerchantfilter.visa.com/" and mapped it to the in-built CloudFront distribution created by Cognito. However, now you want to remove this association. Despite re-mapping the DNS record to an invalid IP address, you are still observing the DNS resolution is intact and pointing "https://oauth.vismerchantfilter.visa.com/" to the CloudFront distribution provisioned by Cognito.
On performing a simple DNS dig lookup along with trace on the domain - "https://oauth.vismerchantfilter.visa.com/", it can be seen that there is a CNAME record that maps "oauth.vismerchantfilter.visa.com" to "d3nq0ha0cpv8fy.cloudfront.net". You can view the same from your end by running the below command.
$ dig +trace oauth.vismerchantfilter.visa.com
The trailing output of the above command indicates that the DNS resolution of the above domain is resolving to a DNS database hosted in Cloudflare, and not Route53. On observing the screenshot you've provided, it appears that the Route53 HostedZone and the results of the DNS/dig trace do not relate to each other. Kindly review the correct DNS database(whether it be Cloudflare or Route53 HostedZone) where the domain 'oauth.vismerchantfilter.visa.com' is hosted and make the required changes accordingly.
For further assistance in identifying the issue or resource based troubleshooting, please raise a support case with AWS. If a support case has already been created please be assured that we will get back to you and assist you in the best way possible.
Thank you for being a valued AWS customer.
AWS Customer Support
Relevant content
asked 2 years ago
asked 5 years ago
