Windows 10: Windows NSLOOKUP DNS Timeouts when resolving, but resolves after 2 seconds

ISSUE: Windows 10, nslookup timesout for 2 secs when doing lookup for custom domain. Basically, any resolution for subdomain/domain that that I attempt, timesout first but then returns. This does not happen with external/Internet domain.

For example, let's say my domain is called www.example.com', the resolution timesout even if the query is repeated:

https://preview.redd.it/otzqlnybuwd...bp&s=1d28a743d70d96882d613c033c0a0bc44918bf7b

Any clue why that's the case? Even though the Internet connectivity is fine on the client, I'm concerned about the delays in resolution when using browser. In other words, "delayed browsing experience".

Thanks

submitted by /u/rsaanon
[link] [comments]

:)

 

DNS does not resolve for download.microsoft.com

I turned off Windows Firewall and ran the following commands here are the results:

Microsoft Windows [Version 10.0.14393]

(c) 2016 Microsoft Corporation. All rights reserved.

C:\WINDOWS\system32>ping download.microsoft.com

Ping request could not find host download.microsoft.com. Please check the name and try again.

C:\WINDOWS\system32>nslookup download.microsoft.com

Server: UnKnown

Address: 8.8.8.8

Non-authoritative answer:

Name: download.microsoft.com

Address: 0.0.0.0

C:\WINDOWS\system32>nslookup download.microsoft.com 208.67.222.222

DNS request timed out.

timeout was 2 seconds.

Server: UnKnown

Address: 208.67.222.222

DNS request timed out.

timeout was 2 seconds.

DNS request timed out.

timeout was 2 seconds.

DNS request timed out.

timeout was 2 seconds.

DNS request timed out.

timeout was 2 seconds.

*** Request to UnKnown timed-out

C:\WINDOWS\system32>

 

DNS resolution lag across entire machine, other PCs on network fine?


I have an issue that I have never seen before. The core problem is that often, when I go to websites, Chrome seems to be stuck on “resolving host” for 4 to 10 seconds, and eventually brings the website up. The same DNS lookup lag happens in Firefox, Edge, and IE as well.

I have tried connecting via both wired and wireless, and get the same issue either way.

I have tried disabling IPv6, no help. I also tried with both the ISP-provided DNS serves and Google DNS servers (8.8.8.8/8.8.4.4), same trouble either way.

We have another PC on the same network, also wired, that has NO trouble with DNS, websites come up very fast. We've even swapped the router plug spots, to no avail.

On the problem PC I’ve even gone to a command prompt and typed in “nslookup”, and sometimes I get timeouts right away. Sometimes nslookup says:

Default Server: Unknown
Address: 24.223.0.16

And sometimes it says:

Default Server: sulfur.intertech.net
Address: 24.223.0.16

Either way, when I type in a domain like yahoo.com at the prompt, I often get:

DNS request times out
Timeout was 2 seconds
DNS request times out
Timeout was 2 seconds
DNS request times out
Timeout was 2 seconds
DNS request times out
Timeout was 2 seconds

…for a bit. On the other hand, sometimes I don’t get any timeouts and the nslookup just resolves the way it’s supposed to.

My security/firewall is the basic Windows Defender built in one. This computer is a brand new windows 10 desktop.

Whatever do I do now? Having most webpages take 5-10 seconds before the DNS resolves and the page loads is driving us nuts! Why is DNS so compromised on this PC, regardless of DNS server specified, regardless of which network adapter (wired or wireless) I use? What’s my next step??

Thanks.

 

tracert not resolving IP to DNS

Hi All,

When I place a tracert command to a certain destination it's not resolving the correct DNS name. But if I run the " nslookup " it works fine. Is any one have any idea about this issue ??

Please note :-

In my network configurations I have 2 DNS servers ( primary and secondary )