Route53 domain and subdomain and fourth level wildcard? Unicorn Meta Zoo #1: Why another podcast? Announcing the arrival of Valued Associate #679: Cesar Manara Come Celebrate our 10 Year Anniversary!How do I set an MX record in Route53 for a GoDaddy domain?Route53 only for wildcard subdomainHow to set up multitenant Route53 subdomains with parent domain not on Route53?Subdomain NameServers to control fourth level domains using Route53?DNS A record is not working with Amazon Route 53Dynamic DNS for subdomain using AWS & Route53How do I Delegate a subdomain to Route53Serving a S3 static website from a naked domain, without migrating to AWS Route53how to add subdomain using route53 and godaddyDNS CNAME to NS record for AWS

How do I deal with an erroneously large refund?

Does using the Inspiration rules for character defects encourage My Guy Syndrome?

Bright yellow or light yellow?

Like totally amazing interchangeable sister outfit accessory swapping or whatever

What is the ongoing value of the Kanban board to the developers as opposed to management

/bin/ls sorts differently than just ls

What is the numbering system used for the DSN dishes?

Raising a bilingual kid. When should we introduce the majority language?

What is a 'Key' in computer science?

Where can I find how to tex symbols for different fonts?

Is there a verb for listening stealthily?

What do you call an IPA symbol that lacks a name (e.g. ɲ)?

Arriving in Atlanta after US Preclearance in Dublin. Will I go through TSA security in Atlanta to transfer to a connecting flight?

What helicopter has the most rotor blades?

When I export an AI 300x60 art board it saves with bigger dimensions

How was Lagrange appointed professor of mathematics so early?

`FindRoot [ ]`::jsing: Encountered a singular Jacobian at a point...WHY

Why did Israel vote against lifting the American embargo on Cuba?

Does Prince Arnaud cause someone holding the Princess to lose?

Could a cockatrice have parasitic embryos?

Why did Europeans not widely domesticate foxes?

Is Bran literally the world's memory?

What is the purpose of the side handle on a hand ("eggbeater") drill?

Philosophers who were composers?



Route53 domain and subdomain and fourth level wildcard?



Unicorn Meta Zoo #1: Why another podcast?
Announcing the arrival of Valued Associate #679: Cesar Manara
Come Celebrate our 10 Year Anniversary!How do I set an MX record in Route53 for a GoDaddy domain?Route53 only for wildcard subdomainHow to set up multitenant Route53 subdomains with parent domain not on Route53?Subdomain NameServers to control fourth level domains using Route53?DNS A record is not working with Amazon Route 53Dynamic DNS for subdomain using AWS & Route53How do I Delegate a subdomain to Route53Serving a S3 static website from a naked domain, without migrating to AWS Route53how to add subdomain using route53 and godaddyDNS CNAME to NS record for AWS



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








2















I'm trying to configure a domain name setup like below and having trouble with Route53.



base.com
sub.base.com
*.sub.base.com => CNAME sub.base.com


I've attempt to create a new hosted zone sub.base.com and add the NS records to base.com. This does appear to delegate (though I'm not sure it is necessary on AWS). I then add the wildcard CNAME to the sub.base.com Zone, and also add an A record to the zone. Now when I lookup a name (dig demo.sub.base.com) dig just gives me back the SOA record and doesn't resolve to the A record.



How should I be configuring this domain layout?










share|improve this question




























    2















    I'm trying to configure a domain name setup like below and having trouble with Route53.



    base.com
    sub.base.com
    *.sub.base.com => CNAME sub.base.com


    I've attempt to create a new hosted zone sub.base.com and add the NS records to base.com. This does appear to delegate (though I'm not sure it is necessary on AWS). I then add the wildcard CNAME to the sub.base.com Zone, and also add an A record to the zone. Now when I lookup a name (dig demo.sub.base.com) dig just gives me back the SOA record and doesn't resolve to the A record.



    How should I be configuring this domain layout?










    share|improve this question
























      2












      2








      2


      2






      I'm trying to configure a domain name setup like below and having trouble with Route53.



      base.com
      sub.base.com
      *.sub.base.com => CNAME sub.base.com


      I've attempt to create a new hosted zone sub.base.com and add the NS records to base.com. This does appear to delegate (though I'm not sure it is necessary on AWS). I then add the wildcard CNAME to the sub.base.com Zone, and also add an A record to the zone. Now when I lookup a name (dig demo.sub.base.com) dig just gives me back the SOA record and doesn't resolve to the A record.



      How should I be configuring this domain layout?










      share|improve this question














      I'm trying to configure a domain name setup like below and having trouble with Route53.



      base.com
      sub.base.com
      *.sub.base.com => CNAME sub.base.com


      I've attempt to create a new hosted zone sub.base.com and add the NS records to base.com. This does appear to delegate (though I'm not sure it is necessary on AWS). I then add the wildcard CNAME to the sub.base.com Zone, and also add an A record to the zone. Now when I lookup a name (dig demo.sub.base.com) dig just gives me back the SOA record and doesn't resolve to the A record.



      How should I be configuring this domain layout?







      domain-name-system amazon-route53






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Jan 28 '14 at 10:30









      edA-qa mort-ora-yedA-qa mort-ora-y

      16019




      16019




















          2 Answers
          2






          active

          oldest

          votes


















          0














          Amazon says that Route53 was not designed to have its Name Servers hit directly, as these were designed to be hit by other DNS servers. This is why the A record past the CNAME will not resolve, because it will not iterate to the server that owns the A record. Further more it is not suggested to use the Route53 NS as your resolver.



          For CNAME records route53 is authoritative for the CNAME record but not for the A record the CNAME points to. If this was a valid domain that was registered, delegated to Route 53 and you were using a non-route53 DNS server for resolving, this would work.



          In conclusion, it you interrogate the DNS server that points to the servers in the route53 delegation zone it would work. If you interrogate one of the servers in the delegation zone directly it will NOT work for CNAMEs.



          I know it could be hard to understand but if you give it an extra read it will make sense.






          share|improve this answer























          • I don't think I understand that. But anyway, I'm looking more for how I should do it rather than understand why it doesn't work. I have no preference to the structure the DNS records should have, I just want something that will have my intended resolution working.

            – edA-qa mort-ora-y
            Jan 28 '14 at 16:13


















          0















          I've attempt to create a new hosted zone sub.base.com and add the NS records to base.com. This does appear to delegate (though I'm not sure it is necessary on AWS).




          This is necessary anytime you delegate, it's not specific to AWS.




          I then add the wildcard CNAME to the sub.base.com Zone, and also add an A record to the zone. Now when I lookup a name (dig demo.sub.base.com) dig just gives me back the SOA record and doesn't resolve to the A record.




          The reason you are getting an SOA back is that demo.sub.base.com does not exists in sub.base.com zone. This is best visualized using dig +trace demo.sub.base.com via command prompt or http://digwebinterface.com/.




          How should I be configuring this domain layout?




          Remove the CNAME from the base.com zone and configure your demo.sub.base.com record in the sub.base.com zone. Then create *.sub.base.com in the sub.base.com zone as a CNAME to demo.sub.base.com.






          share|improve this answer























            Your Answer








            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "2"
            ;
            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%2fserverfault.com%2fquestions%2f570391%2froute53-domain-and-subdomain-and-fourth-level-wildcard%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














            Amazon says that Route53 was not designed to have its Name Servers hit directly, as these were designed to be hit by other DNS servers. This is why the A record past the CNAME will not resolve, because it will not iterate to the server that owns the A record. Further more it is not suggested to use the Route53 NS as your resolver.



            For CNAME records route53 is authoritative for the CNAME record but not for the A record the CNAME points to. If this was a valid domain that was registered, delegated to Route 53 and you were using a non-route53 DNS server for resolving, this would work.



            In conclusion, it you interrogate the DNS server that points to the servers in the route53 delegation zone it would work. If you interrogate one of the servers in the delegation zone directly it will NOT work for CNAMEs.



            I know it could be hard to understand but if you give it an extra read it will make sense.






            share|improve this answer























            • I don't think I understand that. But anyway, I'm looking more for how I should do it rather than understand why it doesn't work. I have no preference to the structure the DNS records should have, I just want something that will have my intended resolution working.

              – edA-qa mort-ora-y
              Jan 28 '14 at 16:13















            0














            Amazon says that Route53 was not designed to have its Name Servers hit directly, as these were designed to be hit by other DNS servers. This is why the A record past the CNAME will not resolve, because it will not iterate to the server that owns the A record. Further more it is not suggested to use the Route53 NS as your resolver.



            For CNAME records route53 is authoritative for the CNAME record but not for the A record the CNAME points to. If this was a valid domain that was registered, delegated to Route 53 and you were using a non-route53 DNS server for resolving, this would work.



            In conclusion, it you interrogate the DNS server that points to the servers in the route53 delegation zone it would work. If you interrogate one of the servers in the delegation zone directly it will NOT work for CNAMEs.



            I know it could be hard to understand but if you give it an extra read it will make sense.






            share|improve this answer























            • I don't think I understand that. But anyway, I'm looking more for how I should do it rather than understand why it doesn't work. I have no preference to the structure the DNS records should have, I just want something that will have my intended resolution working.

              – edA-qa mort-ora-y
              Jan 28 '14 at 16:13













            0












            0








            0







            Amazon says that Route53 was not designed to have its Name Servers hit directly, as these were designed to be hit by other DNS servers. This is why the A record past the CNAME will not resolve, because it will not iterate to the server that owns the A record. Further more it is not suggested to use the Route53 NS as your resolver.



            For CNAME records route53 is authoritative for the CNAME record but not for the A record the CNAME points to. If this was a valid domain that was registered, delegated to Route 53 and you were using a non-route53 DNS server for resolving, this would work.



            In conclusion, it you interrogate the DNS server that points to the servers in the route53 delegation zone it would work. If you interrogate one of the servers in the delegation zone directly it will NOT work for CNAMEs.



            I know it could be hard to understand but if you give it an extra read it will make sense.






            share|improve this answer













            Amazon says that Route53 was not designed to have its Name Servers hit directly, as these were designed to be hit by other DNS servers. This is why the A record past the CNAME will not resolve, because it will not iterate to the server that owns the A record. Further more it is not suggested to use the Route53 NS as your resolver.



            For CNAME records route53 is authoritative for the CNAME record but not for the A record the CNAME points to. If this was a valid domain that was registered, delegated to Route 53 and you were using a non-route53 DNS server for resolving, this would work.



            In conclusion, it you interrogate the DNS server that points to the servers in the route53 delegation zone it would work. If you interrogate one of the servers in the delegation zone directly it will NOT work for CNAMEs.



            I know it could be hard to understand but if you give it an extra read it will make sense.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered Jan 28 '14 at 15:02









            BogdanBogdan

            19016




            19016












            • I don't think I understand that. But anyway, I'm looking more for how I should do it rather than understand why it doesn't work. I have no preference to the structure the DNS records should have, I just want something that will have my intended resolution working.

              – edA-qa mort-ora-y
              Jan 28 '14 at 16:13

















            • I don't think I understand that. But anyway, I'm looking more for how I should do it rather than understand why it doesn't work. I have no preference to the structure the DNS records should have, I just want something that will have my intended resolution working.

              – edA-qa mort-ora-y
              Jan 28 '14 at 16:13
















            I don't think I understand that. But anyway, I'm looking more for how I should do it rather than understand why it doesn't work. I have no preference to the structure the DNS records should have, I just want something that will have my intended resolution working.

            – edA-qa mort-ora-y
            Jan 28 '14 at 16:13





            I don't think I understand that. But anyway, I'm looking more for how I should do it rather than understand why it doesn't work. I have no preference to the structure the DNS records should have, I just want something that will have my intended resolution working.

            – edA-qa mort-ora-y
            Jan 28 '14 at 16:13













            0















            I've attempt to create a new hosted zone sub.base.com and add the NS records to base.com. This does appear to delegate (though I'm not sure it is necessary on AWS).




            This is necessary anytime you delegate, it's not specific to AWS.




            I then add the wildcard CNAME to the sub.base.com Zone, and also add an A record to the zone. Now when I lookup a name (dig demo.sub.base.com) dig just gives me back the SOA record and doesn't resolve to the A record.




            The reason you are getting an SOA back is that demo.sub.base.com does not exists in sub.base.com zone. This is best visualized using dig +trace demo.sub.base.com via command prompt or http://digwebinterface.com/.




            How should I be configuring this domain layout?




            Remove the CNAME from the base.com zone and configure your demo.sub.base.com record in the sub.base.com zone. Then create *.sub.base.com in the sub.base.com zone as a CNAME to demo.sub.base.com.






            share|improve this answer



























              0















              I've attempt to create a new hosted zone sub.base.com and add the NS records to base.com. This does appear to delegate (though I'm not sure it is necessary on AWS).




              This is necessary anytime you delegate, it's not specific to AWS.




              I then add the wildcard CNAME to the sub.base.com Zone, and also add an A record to the zone. Now when I lookup a name (dig demo.sub.base.com) dig just gives me back the SOA record and doesn't resolve to the A record.




              The reason you are getting an SOA back is that demo.sub.base.com does not exists in sub.base.com zone. This is best visualized using dig +trace demo.sub.base.com via command prompt or http://digwebinterface.com/.




              How should I be configuring this domain layout?




              Remove the CNAME from the base.com zone and configure your demo.sub.base.com record in the sub.base.com zone. Then create *.sub.base.com in the sub.base.com zone as a CNAME to demo.sub.base.com.






              share|improve this answer

























                0












                0








                0








                I've attempt to create a new hosted zone sub.base.com and add the NS records to base.com. This does appear to delegate (though I'm not sure it is necessary on AWS).




                This is necessary anytime you delegate, it's not specific to AWS.




                I then add the wildcard CNAME to the sub.base.com Zone, and also add an A record to the zone. Now when I lookup a name (dig demo.sub.base.com) dig just gives me back the SOA record and doesn't resolve to the A record.




                The reason you are getting an SOA back is that demo.sub.base.com does not exists in sub.base.com zone. This is best visualized using dig +trace demo.sub.base.com via command prompt or http://digwebinterface.com/.




                How should I be configuring this domain layout?




                Remove the CNAME from the base.com zone and configure your demo.sub.base.com record in the sub.base.com zone. Then create *.sub.base.com in the sub.base.com zone as a CNAME to demo.sub.base.com.






                share|improve this answer














                I've attempt to create a new hosted zone sub.base.com and add the NS records to base.com. This does appear to delegate (though I'm not sure it is necessary on AWS).




                This is necessary anytime you delegate, it's not specific to AWS.




                I then add the wildcard CNAME to the sub.base.com Zone, and also add an A record to the zone. Now when I lookup a name (dig demo.sub.base.com) dig just gives me back the SOA record and doesn't resolve to the A record.




                The reason you are getting an SOA back is that demo.sub.base.com does not exists in sub.base.com zone. This is best visualized using dig +trace demo.sub.base.com via command prompt or http://digwebinterface.com/.




                How should I be configuring this domain layout?




                Remove the CNAME from the base.com zone and configure your demo.sub.base.com record in the sub.base.com zone. Then create *.sub.base.com in the sub.base.com zone as a CNAME to demo.sub.base.com.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Feb 14 '15 at 5:53









                imperaliximperalix

                30414




                30414



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Server Fault!


                    • 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%2fserverfault.com%2fquestions%2f570391%2froute53-domain-and-subdomain-and-fourth-level-wildcard%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

                    Wikipedia:Vital articles Мазмуну Biography - Өмүр баян Philosophy and psychology - Философия жана психология Religion - Дин Social sciences - Коомдук илимдер Language and literature - Тил жана адабият Science - Илим Technology - Технология Arts and recreation - Искусство жана эс алуу History and geography - Тарых жана география Навигация менюсу

                    Bruxelas-Capital Índice Historia | Composición | Situación lingüística | Clima | Cidades irmandadas | Notas | Véxase tamén | Menú de navegacióneO uso das linguas en Bruxelas e a situación do neerlandés"Rexión de Bruxelas Capital"o orixinalSitio da rexiónPáxina de Bruselas no sitio da Oficina de Promoción Turística de Valonia e BruxelasMapa Interactivo da Rexión de Bruxelas-CapitaleeWorldCat332144929079854441105155190212ID28008674080552-90000 0001 0666 3698n94104302ID540940339365017018237

                    What should I write in an apology letter, since I have decided not to join a company after accepting an offer letterShould I keep looking after accepting a job offer?What should I do when I've been verbally told I would get an offer letter, but still haven't gotten one after 4 weeks?Do I accept an offer from a company that I am not likely to join?New job hasn't confirmed starting date and I want to give current employer as much notice as possibleHow should I address my manager in my resignation letter?HR delayed background verification, now jobless as resignedNo email communication after accepting a formal written offer. How should I phrase the call?What should I do if after receiving a verbal offer letter I am informed that my written job offer is put on hold due to some internal issues?Should I inform the current employer that I am about to resign within 1-2 weeks since I have signed the offer letter and waiting for visa?What company will do, if I send their offer letter to another company