Wired DNS request failure issue












0















From last week, I began to have strange DNS request issue. I have a home DNS server setup to resolve the names of my home PCs. I have 3 windows 10 PCs and 2 synology NASes. One week ago, every thing is fine. But from last week, my windows PCs will lose DNS resolving function after running several hours. This won't happen at the same time for the 3 PCs. If one windows 10 PC has this problem, the others two may be still OK and all the phones and pads are still good. For the PC having problem, you still can ping the DNS server, but just cannot resolve hostname. I tried the following methods:




  1. Disable and enable the network adapter won't make it work.

  2. "ipconfig /flushdns" won't make it work and "ipconfig /displaydns" shows nothing before I flush it.

  3. nslookup just timeout, I tried set the timeout to 10 and even 100. It seems the PC cannot send out the DNS request.


However a simple reboot of the problem PC will make the PC work again. But you don't want to reboot your PC from time to time.



I searched the web and read some posts but didn't find any clue. I don't think it's server issue. It should be the window 10 PCs. Currently, I don't want to reinstall the system. I have kaspersky installed on the 3 PCs and I don't think it's because of virus or hackers. But I'm doubting whether it's because of Kaspersky itself because one weeks ago I also began to have the "self-signed certificate" issue, which is a bug of current version of Kaspersky.
https://forum.kaspersky.com/index.php?/topic/408922-cannot-guarantee-authenticity-of-the-domain-self-signed-certificate-unknown-url/



Hope I can get some answer here. Thanks.










share|improve this question



























    0















    From last week, I began to have strange DNS request issue. I have a home DNS server setup to resolve the names of my home PCs. I have 3 windows 10 PCs and 2 synology NASes. One week ago, every thing is fine. But from last week, my windows PCs will lose DNS resolving function after running several hours. This won't happen at the same time for the 3 PCs. If one windows 10 PC has this problem, the others two may be still OK and all the phones and pads are still good. For the PC having problem, you still can ping the DNS server, but just cannot resolve hostname. I tried the following methods:




    1. Disable and enable the network adapter won't make it work.

    2. "ipconfig /flushdns" won't make it work and "ipconfig /displaydns" shows nothing before I flush it.

    3. nslookup just timeout, I tried set the timeout to 10 and even 100. It seems the PC cannot send out the DNS request.


    However a simple reboot of the problem PC will make the PC work again. But you don't want to reboot your PC from time to time.



    I searched the web and read some posts but didn't find any clue. I don't think it's server issue. It should be the window 10 PCs. Currently, I don't want to reinstall the system. I have kaspersky installed on the 3 PCs and I don't think it's because of virus or hackers. But I'm doubting whether it's because of Kaspersky itself because one weeks ago I also began to have the "self-signed certificate" issue, which is a bug of current version of Kaspersky.
    https://forum.kaspersky.com/index.php?/topic/408922-cannot-guarantee-authenticity-of-the-domain-self-signed-certificate-unknown-url/



    Hope I can get some answer here. Thanks.










    share|improve this question

























      0












      0








      0








      From last week, I began to have strange DNS request issue. I have a home DNS server setup to resolve the names of my home PCs. I have 3 windows 10 PCs and 2 synology NASes. One week ago, every thing is fine. But from last week, my windows PCs will lose DNS resolving function after running several hours. This won't happen at the same time for the 3 PCs. If one windows 10 PC has this problem, the others two may be still OK and all the phones and pads are still good. For the PC having problem, you still can ping the DNS server, but just cannot resolve hostname. I tried the following methods:




      1. Disable and enable the network adapter won't make it work.

      2. "ipconfig /flushdns" won't make it work and "ipconfig /displaydns" shows nothing before I flush it.

      3. nslookup just timeout, I tried set the timeout to 10 and even 100. It seems the PC cannot send out the DNS request.


      However a simple reboot of the problem PC will make the PC work again. But you don't want to reboot your PC from time to time.



      I searched the web and read some posts but didn't find any clue. I don't think it's server issue. It should be the window 10 PCs. Currently, I don't want to reinstall the system. I have kaspersky installed on the 3 PCs and I don't think it's because of virus or hackers. But I'm doubting whether it's because of Kaspersky itself because one weeks ago I also began to have the "self-signed certificate" issue, which is a bug of current version of Kaspersky.
      https://forum.kaspersky.com/index.php?/topic/408922-cannot-guarantee-authenticity-of-the-domain-self-signed-certificate-unknown-url/



      Hope I can get some answer here. Thanks.










      share|improve this question














      From last week, I began to have strange DNS request issue. I have a home DNS server setup to resolve the names of my home PCs. I have 3 windows 10 PCs and 2 synology NASes. One week ago, every thing is fine. But from last week, my windows PCs will lose DNS resolving function after running several hours. This won't happen at the same time for the 3 PCs. If one windows 10 PC has this problem, the others two may be still OK and all the phones and pads are still good. For the PC having problem, you still can ping the DNS server, but just cannot resolve hostname. I tried the following methods:




      1. Disable and enable the network adapter won't make it work.

      2. "ipconfig /flushdns" won't make it work and "ipconfig /displaydns" shows nothing before I flush it.

      3. nslookup just timeout, I tried set the timeout to 10 and even 100. It seems the PC cannot send out the DNS request.


      However a simple reboot of the problem PC will make the PC work again. But you don't want to reboot your PC from time to time.



      I searched the web and read some posts but didn't find any clue. I don't think it's server issue. It should be the window 10 PCs. Currently, I don't want to reinstall the system. I have kaspersky installed on the 3 PCs and I don't think it's because of virus or hackers. But I'm doubting whether it's because of Kaspersky itself because one weeks ago I also began to have the "self-signed certificate" issue, which is a bug of current version of Kaspersky.
      https://forum.kaspersky.com/index.php?/topic/408922-cannot-guarantee-authenticity-of-the-domain-self-signed-certificate-unknown-url/



      Hope I can get some answer here. Thanks.







      windows-10 dns kaspersky






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 23 at 15:28









      johnqhujohnqhu

      12




      12






















          0






          active

          oldest

          votes











          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',
          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%2fsuperuser.com%2fquestions%2f1408787%2fwired-dns-request-failure-issue%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 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.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1408787%2fwired-dns-request-failure-issue%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

          How do I know what Microsoft account the skydrive app is syncing to?

          When does type information flow backwards in C++?

          Grease: Live!