docker how to connect to external DNS












0















I have docker container (lets say A) running on a host (lets say X). I would like the container to be able to have outbound connectivity to a DNS (ie ELB) that host X already has access to.



ie
container A ---> want to be able to curl an external ELB DNS endpoint...problem is container unable to resolve it!



host X ---> is able to curl the external ELB DNS endpoint already










share|improve this question























  • hello? did u try my suggestions?

    – clairestreb
    Nov 25 '18 at 18:12











  • this only mentions ip, does it mean all ports on that ip are mapped? what if same port is on the ip and in the docker container?

    – toop
    Nov 26 '18 at 20:40











  • I added another reference for you in my answer.

    – clairestreb
    Nov 28 '18 at 15:37
















0















I have docker container (lets say A) running on a host (lets say X). I would like the container to be able to have outbound connectivity to a DNS (ie ELB) that host X already has access to.



ie
container A ---> want to be able to curl an external ELB DNS endpoint...problem is container unable to resolve it!



host X ---> is able to curl the external ELB DNS endpoint already










share|improve this question























  • hello? did u try my suggestions?

    – clairestreb
    Nov 25 '18 at 18:12











  • this only mentions ip, does it mean all ports on that ip are mapped? what if same port is on the ip and in the docker container?

    – toop
    Nov 26 '18 at 20:40











  • I added another reference for you in my answer.

    – clairestreb
    Nov 28 '18 at 15:37














0












0








0








I have docker container (lets say A) running on a host (lets say X). I would like the container to be able to have outbound connectivity to a DNS (ie ELB) that host X already has access to.



ie
container A ---> want to be able to curl an external ELB DNS endpoint...problem is container unable to resolve it!



host X ---> is able to curl the external ELB DNS endpoint already










share|improve this question














I have docker container (lets say A) running on a host (lets say X). I would like the container to be able to have outbound connectivity to a DNS (ie ELB) that host X already has access to.



ie
container A ---> want to be able to curl an external ELB DNS endpoint...problem is container unable to resolve it!



host X ---> is able to curl the external ELB DNS endpoint already







docker networking containers






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 22 '18 at 20:27









tooptoop

65




65













  • hello? did u try my suggestions?

    – clairestreb
    Nov 25 '18 at 18:12











  • this only mentions ip, does it mean all ports on that ip are mapped? what if same port is on the ip and in the docker container?

    – toop
    Nov 26 '18 at 20:40











  • I added another reference for you in my answer.

    – clairestreb
    Nov 28 '18 at 15:37



















  • hello? did u try my suggestions?

    – clairestreb
    Nov 25 '18 at 18:12











  • this only mentions ip, does it mean all ports on that ip are mapped? what if same port is on the ip and in the docker container?

    – toop
    Nov 26 '18 at 20:40











  • I added another reference for you in my answer.

    – clairestreb
    Nov 28 '18 at 15:37

















hello? did u try my suggestions?

– clairestreb
Nov 25 '18 at 18:12





hello? did u try my suggestions?

– clairestreb
Nov 25 '18 at 18:12













this only mentions ip, does it mean all ports on that ip are mapped? what if same port is on the ip and in the docker container?

– toop
Nov 26 '18 at 20:40





this only mentions ip, does it mean all ports on that ip are mapped? what if same port is on the ip and in the docker container?

– toop
Nov 26 '18 at 20:40













I added another reference for you in my answer.

– clairestreb
Nov 28 '18 at 15:37





I added another reference for you in my answer.

– clairestreb
Nov 28 '18 at 15:37












1 Answer
1






active

oldest

votes


















1














Do either of these work for you?



$ docker run --dns 10.0.0.2 busybox nslookup google.com


Or edit your /etc/docker/daemon.json similar to:



{
"dns": ["10.0.0.2", "8.8.8.8"]
}


and restart the docker service

$ sudo systemctl docker restart



For more information, please see Fix Docker's networking DNS config and Container networking.






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%2f53437647%2fdocker-how-to-connect-to-external-dns%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    Do either of these work for you?



    $ docker run --dns 10.0.0.2 busybox nslookup google.com


    Or edit your /etc/docker/daemon.json similar to:



    {
    "dns": ["10.0.0.2", "8.8.8.8"]
    }


    and restart the docker service

    $ sudo systemctl docker restart



    For more information, please see Fix Docker's networking DNS config and Container networking.






    share|improve this answer






























      1














      Do either of these work for you?



      $ docker run --dns 10.0.0.2 busybox nslookup google.com


      Or edit your /etc/docker/daemon.json similar to:



      {
      "dns": ["10.0.0.2", "8.8.8.8"]
      }


      and restart the docker service

      $ sudo systemctl docker restart



      For more information, please see Fix Docker's networking DNS config and Container networking.






      share|improve this answer




























        1












        1








        1







        Do either of these work for you?



        $ docker run --dns 10.0.0.2 busybox nslookup google.com


        Or edit your /etc/docker/daemon.json similar to:



        {
        "dns": ["10.0.0.2", "8.8.8.8"]
        }


        and restart the docker service

        $ sudo systemctl docker restart



        For more information, please see Fix Docker's networking DNS config and Container networking.






        share|improve this answer















        Do either of these work for you?



        $ docker run --dns 10.0.0.2 busybox nslookup google.com


        Or edit your /etc/docker/daemon.json similar to:



        {
        "dns": ["10.0.0.2", "8.8.8.8"]
        }


        and restart the docker service

        $ sudo systemctl docker restart



        For more information, please see Fix Docker's networking DNS config and Container networking.







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Nov 28 '18 at 15:37

























        answered Nov 22 '18 at 22:13









        clairestrebclairestreb

        780619




        780619






























            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%2f53437647%2fdocker-how-to-connect-to-external-dns%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

            404 Error Contact Form 7 ajax form submitting

            How to know if a Active Directory user can login interactively

            TypeError: fit_transform() missing 1 required positional argument: 'X'