Answer the question
In order to leave comments, you need to log in
DNS names stopped resolving in Windows 10 how to fix?
I welcome everyone! Tell me what the problem could be, how can I solve it, in general the situation is as follows:
There is Windows 10 x64 Professional 1607 and Windows 7 Ultimate x64 connected to the same router with Internet access via ethernet cable, and suddenly, for no reason at all, on a computer with Win 10 after the next reboot, domain names ceased to be resolved, i.e. any IP addresses on the Internet are pinged, and when you try to ping any Internet name, an error pops up:
C:\Users\User>ping google.ru
Ping request could not find host google.ru. Please check the name and try again.
also with any other Internet domain name, the browser does not go anywhere,
In the properties of the Ethernet connection, the correct IP addresses of the computer, subnet mask, gateway, DNS servers are manually registered, and the DNS servers tried to rewrite different ones - it does not help, and the IP addresses of these DNS servers ping perfectly, and the computer overloaded - it does not help
DNS client service is on
Tried to reset networks, in the network properties - a new option that appeared in Windows 10 - does not help, although usually it always helped with any problems with network settings in Windows 10 before, I tried to follow the advice from the link -
https://gekks.ru/kak-ispravit-oshibki -dns-na-windo...
manually executed commands on the command line as admin:
ipconfig /flushdns
ipconfig /registerdns
ipconfig /release
ipconfig /renew
NETSH winsock reset catalog
NETSH int ipv4 reset reset.log
NETSH int ipv6 reset reset.log
Everything worked OK, rebooted the computer - nothing changed
Deleted the registry keys along the path HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Services. keys Winsock and Winsock2
again executed the commands from above reloaded - still nothing has changed
And even (!) rolled back the system to the last restore point - still nothing has changed (!!!!!!!!!!!!!!!! )
Although at that point at that time everything worked fine!
And that on a neighboring computer with Win7 running through the same router, everything works fine!
Answer the question
In order to leave comments, you need to log in
Alternatively, the firewall blocks DNS ports.
Use the nslookup
ps command to diagnose DNS. this is an assumption that does not always come to mind to check, which is why it was in the form of a comment, not an answer.
Look in the ifconfig output for the addresses of the DNS servers. Using nslookup, make a test request:
It will either give out the Yandex ip-address, or say "Non-existent domain" if it cannot find the address along the chain, or there will be a request timeout.
In the first case, everything should work fine.
In the second case, the DNS server is weird. It can be forced in the settings. 8.8.8.8 Google and/or 1.1.1.1 Cloudfleur.
In the third case, the DNS server is down or unavailable.
Blue - it may be a hematoma, not gangrene. There is no need to immediately amputate the limb. :)
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question