How to trace the route of a DNS query?











up vote
5
down vote

favorite












... up to the DNS server that answers it? When I use the public DNS server provided by Google (8.8.8.8), this is the DNS server reported by "nslookup" (8.8.8.8), however the www.dnsleaktest.com website shows a different IP number, actually two, 74.125.189.22 and 74.125.189.23. Is there a way to trace the route taken by the DNS query from 8.8.8.8 to 74.125.189.22, including other DNS servers eventually queried in-between? I tried nslookup's debug options, but there is no reference to 74.125.189.22 in the debug info.










share|improve this question


























    up vote
    5
    down vote

    favorite












    ... up to the DNS server that answers it? When I use the public DNS server provided by Google (8.8.8.8), this is the DNS server reported by "nslookup" (8.8.8.8), however the www.dnsleaktest.com website shows a different IP number, actually two, 74.125.189.22 and 74.125.189.23. Is there a way to trace the route taken by the DNS query from 8.8.8.8 to 74.125.189.22, including other DNS servers eventually queried in-between? I tried nslookup's debug options, but there is no reference to 74.125.189.22 in the debug info.










    share|improve this question
























      up vote
      5
      down vote

      favorite









      up vote
      5
      down vote

      favorite











      ... up to the DNS server that answers it? When I use the public DNS server provided by Google (8.8.8.8), this is the DNS server reported by "nslookup" (8.8.8.8), however the www.dnsleaktest.com website shows a different IP number, actually two, 74.125.189.22 and 74.125.189.23. Is there a way to trace the route taken by the DNS query from 8.8.8.8 to 74.125.189.22, including other DNS servers eventually queried in-between? I tried nslookup's debug options, but there is no reference to 74.125.189.22 in the debug info.










      share|improve this question













      ... up to the DNS server that answers it? When I use the public DNS server provided by Google (8.8.8.8), this is the DNS server reported by "nslookup" (8.8.8.8), however the www.dnsleaktest.com website shows a different IP number, actually two, 74.125.189.22 and 74.125.189.23. Is there a way to trace the route taken by the DNS query from 8.8.8.8 to 74.125.189.22, including other DNS servers eventually queried in-between? I tried nslookup's debug options, but there is no reference to 74.125.189.22 in the debug info.







      windows-7 dns






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 28 '13 at 12:25









      user285154

      26112




      26112






















          3 Answers
          3






          active

          oldest

          votes

















          up vote
          0
          down vote













          I've never used it myself , but it seems that dnsracer does what you want.



          http://www.mavetju.org/unix/dnstracer.php



          I am not sure there is such a tool available on Windows, but there is an available package in Linux Debian repository.






          share|improve this answer

















          • 2




            It doesn't do what the questioner wants, but what the questioner wants is based upon a fundamental misunderstanding of the operation of the DNS anyway.
            – JdeBP
            Dec 30 '13 at 17:26










          • @JdeBP It would be nice at times to know which DNS server was responsible for resolving a particular address.
            – bvj
            Apr 1 '15 at 19:31










          • It's dead easy to determine that, because it is configured at your end. It's (the anycast instance of) the server at 8.8.8.8, in the case of the question at hand, for example, as configured in Control Panel on that computer. It is there that the process of query resolution happens.
            – JdeBP
            Apr 4 '15 at 19:21


















          up vote
          0
          down vote













          Try going to https://www.grc.com/dns/dns.htm to see which DNS servers you are currently using. Also make sure in your windows network settings that your DNS settings are set to the google dns at 8.8.8.8 and 8.8.4.4.



          As for the 74.125.189.22 IP range still seem to be Google but pointing to Google Translate.



          If I were you I'd follow these steps.





          1. Change TCP/IP Settings in Windows 7 to verify I'm using the above mentioned google DNS.


          2. Use DNS Nameserver Spoofability Test to make sure the only DNS being used is the Google DNS.






          share|improve this answer




























            up vote
            0
            down vote













            I dont believe this is possible. When you make a DNS request, it goes to your DNS server. Your DNS server tries to resolve the name and if it cant, it moves up the DNS name hierarchy, becoming the requester. In short, once a request is made the requester is just waiting for a response from the next server.






            share|improve this answer





















              Your Answer








              StackExchange.ready(function() {
              var channelOptions = {
              tags: "".split(" "),
              id: "3"
              };
              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',
              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%2fsuperuser.com%2fquestions%2f694127%2fhow-to-trace-the-route-of-a-dns-query%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              3 Answers
              3






              active

              oldest

              votes








              3 Answers
              3






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes








              up vote
              0
              down vote













              I've never used it myself , but it seems that dnsracer does what you want.



              http://www.mavetju.org/unix/dnstracer.php



              I am not sure there is such a tool available on Windows, but there is an available package in Linux Debian repository.






              share|improve this answer

















              • 2




                It doesn't do what the questioner wants, but what the questioner wants is based upon a fundamental misunderstanding of the operation of the DNS anyway.
                – JdeBP
                Dec 30 '13 at 17:26










              • @JdeBP It would be nice at times to know which DNS server was responsible for resolving a particular address.
                – bvj
                Apr 1 '15 at 19:31










              • It's dead easy to determine that, because it is configured at your end. It's (the anycast instance of) the server at 8.8.8.8, in the case of the question at hand, for example, as configured in Control Panel on that computer. It is there that the process of query resolution happens.
                – JdeBP
                Apr 4 '15 at 19:21















              up vote
              0
              down vote













              I've never used it myself , but it seems that dnsracer does what you want.



              http://www.mavetju.org/unix/dnstracer.php



              I am not sure there is such a tool available on Windows, but there is an available package in Linux Debian repository.






              share|improve this answer

















              • 2




                It doesn't do what the questioner wants, but what the questioner wants is based upon a fundamental misunderstanding of the operation of the DNS anyway.
                – JdeBP
                Dec 30 '13 at 17:26










              • @JdeBP It would be nice at times to know which DNS server was responsible for resolving a particular address.
                – bvj
                Apr 1 '15 at 19:31










              • It's dead easy to determine that, because it is configured at your end. It's (the anycast instance of) the server at 8.8.8.8, in the case of the question at hand, for example, as configured in Control Panel on that computer. It is there that the process of query resolution happens.
                – JdeBP
                Apr 4 '15 at 19:21













              up vote
              0
              down vote










              up vote
              0
              down vote









              I've never used it myself , but it seems that dnsracer does what you want.



              http://www.mavetju.org/unix/dnstracer.php



              I am not sure there is such a tool available on Windows, but there is an available package in Linux Debian repository.






              share|improve this answer












              I've never used it myself , but it seems that dnsracer does what you want.



              http://www.mavetju.org/unix/dnstracer.php



              I am not sure there is such a tool available on Windows, but there is an available package in Linux Debian repository.







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Dec 28 '13 at 13:25









              user2196728

              1,076710




              1,076710








              • 2




                It doesn't do what the questioner wants, but what the questioner wants is based upon a fundamental misunderstanding of the operation of the DNS anyway.
                – JdeBP
                Dec 30 '13 at 17:26










              • @JdeBP It would be nice at times to know which DNS server was responsible for resolving a particular address.
                – bvj
                Apr 1 '15 at 19:31










              • It's dead easy to determine that, because it is configured at your end. It's (the anycast instance of) the server at 8.8.8.8, in the case of the question at hand, for example, as configured in Control Panel on that computer. It is there that the process of query resolution happens.
                – JdeBP
                Apr 4 '15 at 19:21














              • 2




                It doesn't do what the questioner wants, but what the questioner wants is based upon a fundamental misunderstanding of the operation of the DNS anyway.
                – JdeBP
                Dec 30 '13 at 17:26










              • @JdeBP It would be nice at times to know which DNS server was responsible for resolving a particular address.
                – bvj
                Apr 1 '15 at 19:31










              • It's dead easy to determine that, because it is configured at your end. It's (the anycast instance of) the server at 8.8.8.8, in the case of the question at hand, for example, as configured in Control Panel on that computer. It is there that the process of query resolution happens.
                – JdeBP
                Apr 4 '15 at 19:21








              2




              2




              It doesn't do what the questioner wants, but what the questioner wants is based upon a fundamental misunderstanding of the operation of the DNS anyway.
              – JdeBP
              Dec 30 '13 at 17:26




              It doesn't do what the questioner wants, but what the questioner wants is based upon a fundamental misunderstanding of the operation of the DNS anyway.
              – JdeBP
              Dec 30 '13 at 17:26












              @JdeBP It would be nice at times to know which DNS server was responsible for resolving a particular address.
              – bvj
              Apr 1 '15 at 19:31




              @JdeBP It would be nice at times to know which DNS server was responsible for resolving a particular address.
              – bvj
              Apr 1 '15 at 19:31












              It's dead easy to determine that, because it is configured at your end. It's (the anycast instance of) the server at 8.8.8.8, in the case of the question at hand, for example, as configured in Control Panel on that computer. It is there that the process of query resolution happens.
              – JdeBP
              Apr 4 '15 at 19:21




              It's dead easy to determine that, because it is configured at your end. It's (the anycast instance of) the server at 8.8.8.8, in the case of the question at hand, for example, as configured in Control Panel on that computer. It is there that the process of query resolution happens.
              – JdeBP
              Apr 4 '15 at 19:21












              up vote
              0
              down vote













              Try going to https://www.grc.com/dns/dns.htm to see which DNS servers you are currently using. Also make sure in your windows network settings that your DNS settings are set to the google dns at 8.8.8.8 and 8.8.4.4.



              As for the 74.125.189.22 IP range still seem to be Google but pointing to Google Translate.



              If I were you I'd follow these steps.





              1. Change TCP/IP Settings in Windows 7 to verify I'm using the above mentioned google DNS.


              2. Use DNS Nameserver Spoofability Test to make sure the only DNS being used is the Google DNS.






              share|improve this answer

























                up vote
                0
                down vote













                Try going to https://www.grc.com/dns/dns.htm to see which DNS servers you are currently using. Also make sure in your windows network settings that your DNS settings are set to the google dns at 8.8.8.8 and 8.8.4.4.



                As for the 74.125.189.22 IP range still seem to be Google but pointing to Google Translate.



                If I were you I'd follow these steps.





                1. Change TCP/IP Settings in Windows 7 to verify I'm using the above mentioned google DNS.


                2. Use DNS Nameserver Spoofability Test to make sure the only DNS being used is the Google DNS.






                share|improve this answer























                  up vote
                  0
                  down vote










                  up vote
                  0
                  down vote









                  Try going to https://www.grc.com/dns/dns.htm to see which DNS servers you are currently using. Also make sure in your windows network settings that your DNS settings are set to the google dns at 8.8.8.8 and 8.8.4.4.



                  As for the 74.125.189.22 IP range still seem to be Google but pointing to Google Translate.



                  If I were you I'd follow these steps.





                  1. Change TCP/IP Settings in Windows 7 to verify I'm using the above mentioned google DNS.


                  2. Use DNS Nameserver Spoofability Test to make sure the only DNS being used is the Google DNS.






                  share|improve this answer












                  Try going to https://www.grc.com/dns/dns.htm to see which DNS servers you are currently using. Also make sure in your windows network settings that your DNS settings are set to the google dns at 8.8.8.8 and 8.8.4.4.



                  As for the 74.125.189.22 IP range still seem to be Google but pointing to Google Translate.



                  If I were you I'd follow these steps.





                  1. Change TCP/IP Settings in Windows 7 to verify I'm using the above mentioned google DNS.


                  2. Use DNS Nameserver Spoofability Test to make sure the only DNS being used is the Google DNS.







                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Jan 2 '14 at 6:31









                  meguroyama

                  12019




                  12019






















                      up vote
                      0
                      down vote













                      I dont believe this is possible. When you make a DNS request, it goes to your DNS server. Your DNS server tries to resolve the name and if it cant, it moves up the DNS name hierarchy, becoming the requester. In short, once a request is made the requester is just waiting for a response from the next server.






                      share|improve this answer

























                        up vote
                        0
                        down vote













                        I dont believe this is possible. When you make a DNS request, it goes to your DNS server. Your DNS server tries to resolve the name and if it cant, it moves up the DNS name hierarchy, becoming the requester. In short, once a request is made the requester is just waiting for a response from the next server.






                        share|improve this answer























                          up vote
                          0
                          down vote










                          up vote
                          0
                          down vote









                          I dont believe this is possible. When you make a DNS request, it goes to your DNS server. Your DNS server tries to resolve the name and if it cant, it moves up the DNS name hierarchy, becoming the requester. In short, once a request is made the requester is just waiting for a response from the next server.






                          share|improve this answer












                          I dont believe this is possible. When you make a DNS request, it goes to your DNS server. Your DNS server tries to resolve the name and if it cant, it moves up the DNS name hierarchy, becoming the requester. In short, once a request is made the requester is just waiting for a response from the next server.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Jul 11 '16 at 0:23









                          Keltari

                          50.2k18115168




                          50.2k18115168






























                              draft saved

                              draft discarded




















































                              Thanks for contributing an answer to Super User!


                              • 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.





                              Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                              Please pay close attention to the following guidance:


                              • 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%2fsuperuser.com%2fquestions%2f694127%2fhow-to-trace-the-route-of-a-dns-query%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

                              flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

                              Mangá

                               ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕