AWS route53 domain not resolving to private ubuntu 16.04












0















I have the domain and sub-domain in AWS route 53.



domain.com



sub.domain.com



the 'A' record of sub.domain.com added with the public ip of the instance.



And an ubuntu 16.04 server privately hosted, not in EC2.



Now I am running a service at port 4443.



And it needs to be available in public domain "sub.domain.com"



I have edited the /etc/hosts and /etc/hostnames. So hostname -f gives "sub.domain.com"



I have also used hostnamectl set-hostname sub.domain.com



But still http://sub.domain.com not reaching the service. Not the ip too.



Netstat shows the service is listening at port 5000.



Does anything I missed?










share|improve this question



























    0















    I have the domain and sub-domain in AWS route 53.



    domain.com



    sub.domain.com



    the 'A' record of sub.domain.com added with the public ip of the instance.



    And an ubuntu 16.04 server privately hosted, not in EC2.



    Now I am running a service at port 4443.



    And it needs to be available in public domain "sub.domain.com"



    I have edited the /etc/hosts and /etc/hostnames. So hostname -f gives "sub.domain.com"



    I have also used hostnamectl set-hostname sub.domain.com



    But still http://sub.domain.com not reaching the service. Not the ip too.



    Netstat shows the service is listening at port 5000.



    Does anything I missed?










    share|improve this question

























      0












      0








      0








      I have the domain and sub-domain in AWS route 53.



      domain.com



      sub.domain.com



      the 'A' record of sub.domain.com added with the public ip of the instance.



      And an ubuntu 16.04 server privately hosted, not in EC2.



      Now I am running a service at port 4443.



      And it needs to be available in public domain "sub.domain.com"



      I have edited the /etc/hosts and /etc/hostnames. So hostname -f gives "sub.domain.com"



      I have also used hostnamectl set-hostname sub.domain.com



      But still http://sub.domain.com not reaching the service. Not the ip too.



      Netstat shows the service is listening at port 5000.



      Does anything I missed?










      share|improve this question














      I have the domain and sub-domain in AWS route 53.



      domain.com



      sub.domain.com



      the 'A' record of sub.domain.com added with the public ip of the instance.



      And an ubuntu 16.04 server privately hosted, not in EC2.



      Now I am running a service at port 4443.



      And it needs to be available in public domain "sub.domain.com"



      I have edited the /etc/hosts and /etc/hostnames. So hostname -f gives "sub.domain.com"



      I have also used hostnamectl set-hostname sub.domain.com



      But still http://sub.domain.com not reaching the service. Not the ip too.



      Netstat shows the service is listening at port 5000.



      Does anything I missed?







      linux dns






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 1 hour ago









      sowmiyaksrsowmiyaksr

      153




      153






















          0






          active

          oldest

          votes











          Your Answer








          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "106"
          };
          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: false,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: null,
          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%2funix.stackexchange.com%2fquestions%2f503046%2faws-route53-domain-not-resolving-to-private-ubuntu-16-04%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Unix & Linux Stack Exchange!


          • 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%2funix.stackexchange.com%2fquestions%2f503046%2faws-route53-domain-not-resolving-to-private-ubuntu-16-04%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

          Loup dans la culture

          How to solve the problem of ntp “Unable to contact time server” from KDE?

          ASUS Zenbook UX433/UX333 — Configure Touchpad-embedded numpad on Linux