Timeline for DNS lookups don't work in Windows except immediately after ipconfig /flushdns
Current License: CC BY-SA 3.0
7 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
May 20, 2017 at 19:38 | comment | added | g491 | For time reasons we're just going to try replacing the networking equipment. I tried some stuff like Google DNS and didn't feel that there was a clear path to a solution. I awarded you the bounty for your high quality answer, and if this doesn't solve it, I'll plan to revisit and see if we can figure out what the deal is. Thanks | |
May 19, 2017 at 11:21 | comment | added | I say Reinstate Monica | Did you figure out what is happening to your DNS queries? | |
May 19, 2017 at 6:03 | history | bounty ended | g491 | ||
May 16, 2017 at 2:18 | comment | added | I say Reinstate Monica | @g491 That puzzles me too, but it's more concerning that once things get "working", they're really not working given that you're getting invalid responses to your query. You may find that solving this clearly evident problem also solves the more obscure issue of flushing the cache reviving lookups for a while. | |
May 16, 2017 at 2:09 | comment | added | g491 | Why would running `ipconfig /flushdns temporarily get things working on this computer? What's so weird is all the other systems on the network are fine and this computer used to be fine as well. | |
May 15, 2017 at 19:00 | history | edited | I say Reinstate Monica | CC BY-SA 3.0 |
added 715 characters in body
|
May 15, 2017 at 18:51 | history | answered | I say Reinstate Monica | CC BY-SA 3.0 |