AWS Certificate Request Validation Timeout





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















I'm trying to request a certificate using AWS certificate manager. I'm using route53 for DNS. I go through all of the steps, and use the "create record in Route53" to create the CNAME record automatically. I have double checked the CNAME record in Route53 to make sure it is the same one that ACM expects. After doing all of this, the DNS validation times out.



I have tried this multiple times with the same result. I barely know how to use dig so I'm kind of lost on how to troubleshoot this. Thanks.










share|improve this question





























    0















    I'm trying to request a certificate using AWS certificate manager. I'm using route53 for DNS. I go through all of the steps, and use the "create record in Route53" to create the CNAME record automatically. I have double checked the CNAME record in Route53 to make sure it is the same one that ACM expects. After doing all of this, the DNS validation times out.



    I have tried this multiple times with the same result. I barely know how to use dig so I'm kind of lost on how to troubleshoot this. Thanks.










    share|improve this question

























      0












      0








      0








      I'm trying to request a certificate using AWS certificate manager. I'm using route53 for DNS. I go through all of the steps, and use the "create record in Route53" to create the CNAME record automatically. I have double checked the CNAME record in Route53 to make sure it is the same one that ACM expects. After doing all of this, the DNS validation times out.



      I have tried this multiple times with the same result. I barely know how to use dig so I'm kind of lost on how to troubleshoot this. Thanks.










      share|improve this question














      I'm trying to request a certificate using AWS certificate manager. I'm using route53 for DNS. I go through all of the steps, and use the "create record in Route53" to create the CNAME record automatically. I have double checked the CNAME record in Route53 to make sure it is the same one that ACM expects. After doing all of this, the DNS validation times out.



      I have tried this multiple times with the same result. I barely know how to use dig so I'm kind of lost on how to troubleshoot this. Thanks.







      amazon-route53 aws-certificate-manager






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 3 at 15:53









      Max PaymarMax Paymar

      285219




      285219
























          2 Answers
          2






          active

          oldest

          votes


















          0














          I was facing a similar issue, where i copied the whole "name" of the CNAME record (from the AWS certificate manager) to the DNS configuration for my domain. And waited a whole day without any success. Then after reading "Michael - sqlbot" answer here, i removed the .example.com from _9022ecb910c52234234234234232xxxx.example.com in my domain's DNS configuration and Amazon Certificate Manager issued the certificate in about next 30 mins.



          Hope you are not making the same mistake :-)






          share|improve this answer
























          • Hi - thanks for your reply. I'm using the "Create Record in Route53" button after creating the certificate, so AWS creates the record for me. I double checked and it's not using .example.com. I tried using dig to troubleshoot and I'm getting this response for querying the CNAME record (and A record for that matter)id 60031 opcode QUERY rcode SERVFAIL flags QR RD RA ;QUESTION maxpaymar.com. IN CNAME ;ANSWER ;AUTHORITY ;ADDITIONAL

            – Max Paymar
            Jan 6 at 5:44













          • I am not an expert in using Dig, but there are two things, that indicate a problem, that i can see in the response you get from Dig. 1. rcode SERVFAIL - i get rcode NOERROR 2. ;QUESTION maxpaymar.com. IN CNAME ; ANSWER <blank> Whereas what i get is.. ;QUESTION www.mydomain.com. IN CNAME ;ANSWER www.mydomain.com. 3599 IN CNAME d2xxw7xx19mpsi.cloudfront.net.

            – Afshar
            Jan 6 at 7:04



















          0














          When I switched my domain from godaddy to AWS, the Name Server records did not automatically update. I thought they would but I actually had to change them manually from the AWS console.






          share|improve this answer
























            Your Answer






            StackExchange.ifUsing("editor", function () {
            StackExchange.using("externalEditor", function () {
            StackExchange.using("snippets", function () {
            StackExchange.snippets.init();
            });
            });
            }, "code-snippets");

            StackExchange.ready(function() {
            var channelOptions = {
            tags: "".split(" "),
            id: "1"
            };
            initTagRenderer("".split(" "), "".split(" "), channelOptions);

            StackExchange.using("externalEditor", function() {
            // Have to fire editor after snippets, if snippets enabled
            if (StackExchange.settings.snippets.snippetsEnabled) {
            StackExchange.using("snippets", function() {
            createEditor();
            });
            }
            else {
            createEditor();
            }
            });

            function createEditor() {
            StackExchange.prepareEditor({
            heartbeatType: 'answer',
            autoActivateHeartbeat: false,
            convertImagesToLinks: true,
            noModals: true,
            showLowRepImageUploadWarning: true,
            reputationToPostImages: 10,
            bindNavPrevention: true,
            postfix: "",
            imageUploader: {
            brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
            contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
            allowUrls: true
            },
            onDemand: true,
            discardSelector: ".discard-answer"
            ,immediatelyShowMarkdownHelp:true
            });


            }
            });














            draft saved

            draft discarded


















            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54025660%2faws-certificate-request-validation-timeout%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            I was facing a similar issue, where i copied the whole "name" of the CNAME record (from the AWS certificate manager) to the DNS configuration for my domain. And waited a whole day without any success. Then after reading "Michael - sqlbot" answer here, i removed the .example.com from _9022ecb910c52234234234234232xxxx.example.com in my domain's DNS configuration and Amazon Certificate Manager issued the certificate in about next 30 mins.



            Hope you are not making the same mistake :-)






            share|improve this answer
























            • Hi - thanks for your reply. I'm using the "Create Record in Route53" button after creating the certificate, so AWS creates the record for me. I double checked and it's not using .example.com. I tried using dig to troubleshoot and I'm getting this response for querying the CNAME record (and A record for that matter)id 60031 opcode QUERY rcode SERVFAIL flags QR RD RA ;QUESTION maxpaymar.com. IN CNAME ;ANSWER ;AUTHORITY ;ADDITIONAL

              – Max Paymar
              Jan 6 at 5:44













            • I am not an expert in using Dig, but there are two things, that indicate a problem, that i can see in the response you get from Dig. 1. rcode SERVFAIL - i get rcode NOERROR 2. ;QUESTION maxpaymar.com. IN CNAME ; ANSWER <blank> Whereas what i get is.. ;QUESTION www.mydomain.com. IN CNAME ;ANSWER www.mydomain.com. 3599 IN CNAME d2xxw7xx19mpsi.cloudfront.net.

              – Afshar
              Jan 6 at 7:04
















            0














            I was facing a similar issue, where i copied the whole "name" of the CNAME record (from the AWS certificate manager) to the DNS configuration for my domain. And waited a whole day without any success. Then after reading "Michael - sqlbot" answer here, i removed the .example.com from _9022ecb910c52234234234234232xxxx.example.com in my domain's DNS configuration and Amazon Certificate Manager issued the certificate in about next 30 mins.



            Hope you are not making the same mistake :-)






            share|improve this answer
























            • Hi - thanks for your reply. I'm using the "Create Record in Route53" button after creating the certificate, so AWS creates the record for me. I double checked and it's not using .example.com. I tried using dig to troubleshoot and I'm getting this response for querying the CNAME record (and A record for that matter)id 60031 opcode QUERY rcode SERVFAIL flags QR RD RA ;QUESTION maxpaymar.com. IN CNAME ;ANSWER ;AUTHORITY ;ADDITIONAL

              – Max Paymar
              Jan 6 at 5:44













            • I am not an expert in using Dig, but there are two things, that indicate a problem, that i can see in the response you get from Dig. 1. rcode SERVFAIL - i get rcode NOERROR 2. ;QUESTION maxpaymar.com. IN CNAME ; ANSWER <blank> Whereas what i get is.. ;QUESTION www.mydomain.com. IN CNAME ;ANSWER www.mydomain.com. 3599 IN CNAME d2xxw7xx19mpsi.cloudfront.net.

              – Afshar
              Jan 6 at 7:04














            0












            0








            0







            I was facing a similar issue, where i copied the whole "name" of the CNAME record (from the AWS certificate manager) to the DNS configuration for my domain. And waited a whole day without any success. Then after reading "Michael - sqlbot" answer here, i removed the .example.com from _9022ecb910c52234234234234232xxxx.example.com in my domain's DNS configuration and Amazon Certificate Manager issued the certificate in about next 30 mins.



            Hope you are not making the same mistake :-)






            share|improve this answer













            I was facing a similar issue, where i copied the whole "name" of the CNAME record (from the AWS certificate manager) to the DNS configuration for my domain. And waited a whole day without any success. Then after reading "Michael - sqlbot" answer here, i removed the .example.com from _9022ecb910c52234234234234232xxxx.example.com in my domain's DNS configuration and Amazon Certificate Manager issued the certificate in about next 30 mins.



            Hope you are not making the same mistake :-)







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jan 5 at 16:29









            AfsharAfshar

            14227




            14227













            • Hi - thanks for your reply. I'm using the "Create Record in Route53" button after creating the certificate, so AWS creates the record for me. I double checked and it's not using .example.com. I tried using dig to troubleshoot and I'm getting this response for querying the CNAME record (and A record for that matter)id 60031 opcode QUERY rcode SERVFAIL flags QR RD RA ;QUESTION maxpaymar.com. IN CNAME ;ANSWER ;AUTHORITY ;ADDITIONAL

              – Max Paymar
              Jan 6 at 5:44













            • I am not an expert in using Dig, but there are two things, that indicate a problem, that i can see in the response you get from Dig. 1. rcode SERVFAIL - i get rcode NOERROR 2. ;QUESTION maxpaymar.com. IN CNAME ; ANSWER <blank> Whereas what i get is.. ;QUESTION www.mydomain.com. IN CNAME ;ANSWER www.mydomain.com. 3599 IN CNAME d2xxw7xx19mpsi.cloudfront.net.

              – Afshar
              Jan 6 at 7:04



















            • Hi - thanks for your reply. I'm using the "Create Record in Route53" button after creating the certificate, so AWS creates the record for me. I double checked and it's not using .example.com. I tried using dig to troubleshoot and I'm getting this response for querying the CNAME record (and A record for that matter)id 60031 opcode QUERY rcode SERVFAIL flags QR RD RA ;QUESTION maxpaymar.com. IN CNAME ;ANSWER ;AUTHORITY ;ADDITIONAL

              – Max Paymar
              Jan 6 at 5:44













            • I am not an expert in using Dig, but there are two things, that indicate a problem, that i can see in the response you get from Dig. 1. rcode SERVFAIL - i get rcode NOERROR 2. ;QUESTION maxpaymar.com. IN CNAME ; ANSWER <blank> Whereas what i get is.. ;QUESTION www.mydomain.com. IN CNAME ;ANSWER www.mydomain.com. 3599 IN CNAME d2xxw7xx19mpsi.cloudfront.net.

              – Afshar
              Jan 6 at 7:04

















            Hi - thanks for your reply. I'm using the "Create Record in Route53" button after creating the certificate, so AWS creates the record for me. I double checked and it's not using .example.com. I tried using dig to troubleshoot and I'm getting this response for querying the CNAME record (and A record for that matter)id 60031 opcode QUERY rcode SERVFAIL flags QR RD RA ;QUESTION maxpaymar.com. IN CNAME ;ANSWER ;AUTHORITY ;ADDITIONAL

            – Max Paymar
            Jan 6 at 5:44







            Hi - thanks for your reply. I'm using the "Create Record in Route53" button after creating the certificate, so AWS creates the record for me. I double checked and it's not using .example.com. I tried using dig to troubleshoot and I'm getting this response for querying the CNAME record (and A record for that matter)id 60031 opcode QUERY rcode SERVFAIL flags QR RD RA ;QUESTION maxpaymar.com. IN CNAME ;ANSWER ;AUTHORITY ;ADDITIONAL

            – Max Paymar
            Jan 6 at 5:44















            I am not an expert in using Dig, but there are two things, that indicate a problem, that i can see in the response you get from Dig. 1. rcode SERVFAIL - i get rcode NOERROR 2. ;QUESTION maxpaymar.com. IN CNAME ; ANSWER <blank> Whereas what i get is.. ;QUESTION www.mydomain.com. IN CNAME ;ANSWER www.mydomain.com. 3599 IN CNAME d2xxw7xx19mpsi.cloudfront.net.

            – Afshar
            Jan 6 at 7:04





            I am not an expert in using Dig, but there are two things, that indicate a problem, that i can see in the response you get from Dig. 1. rcode SERVFAIL - i get rcode NOERROR 2. ;QUESTION maxpaymar.com. IN CNAME ; ANSWER <blank> Whereas what i get is.. ;QUESTION www.mydomain.com. IN CNAME ;ANSWER www.mydomain.com. 3599 IN CNAME d2xxw7xx19mpsi.cloudfront.net.

            – Afshar
            Jan 6 at 7:04













            0














            When I switched my domain from godaddy to AWS, the Name Server records did not automatically update. I thought they would but I actually had to change them manually from the AWS console.






            share|improve this answer




























              0














              When I switched my domain from godaddy to AWS, the Name Server records did not automatically update. I thought they would but I actually had to change them manually from the AWS console.






              share|improve this answer


























                0












                0








                0







                When I switched my domain from godaddy to AWS, the Name Server records did not automatically update. I thought they would but I actually had to change them manually from the AWS console.






                share|improve this answer













                When I switched my domain from godaddy to AWS, the Name Server records did not automatically update. I thought they would but I actually had to change them manually from the AWS console.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Mar 7 at 16:23









                Max PaymarMax Paymar

                285219




                285219






























                    draft saved

                    draft discarded




















































                    Thanks for contributing an answer to Stack Overflow!


                    • Please be sure to answer the question. Provide details and share your research!

                    But avoid



                    • Asking for help, clarification, or responding to other answers.

                    • Making statements based on opinion; back them up with references or personal experience.


                    To learn more, see our tips on writing great answers.




                    draft saved


                    draft discarded














                    StackExchange.ready(
                    function () {
                    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54025660%2faws-certificate-request-validation-timeout%23new-answer', 'question_page');
                    }
                    );

                    Post as a guest















                    Required, but never shown





















































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown

































                    Required, but never shown














                    Required, but never shown












                    Required, but never shown







                    Required, but never shown







                    Popular posts from this blog

                    MongoDB - Not Authorized To Execute Command

                    How to fix TextFormField cause rebuild widget in Flutter

                    Npm cannot find a required file even through it is in the searched directory