Windows 10 can't resolve hostnames - ping with IP works but not with hostname
Facts:
- The browser doesn't load any pages, whether they are addressed with IP or hostname.
ping google.com
doesn't work, returningPing request could not find host google.com.
ping 216.58.209.78
(google IP) does work, sending and receiving all packets.
nslookup google.com
does work, returning correct IP address that then does indeed work withping
.- Network settings are default, IP and DNS are set to auto.
- Specifying OpenDNS in network settings does not help.
- There are no entries in
c:windowssystem32driversetchost
- There are no DNS prefixes in use.
netsh winsock reset & netsh int ip reset
does not help.- DNS client is running.
- The most common given solution on the Internet
ipconfig /flushdns & ipconfig /registerdns
does not work, with latter returningRegistration of DNS records failed: Parameter is not correct.
It happens occassionally to people, but I have not found possible solutions to this problem. I sense this might be the key to my ordeal. - All of the above happens for different networks.
- The PC has been recently formatted. One guy had the same problem and it helped to restore the previous PC name, but I have no way of finding what the name was before the format.
ipconfig /all
is as below. The first paragraph looks a bit blank, perhaps something there...?
Windows IP Configuration
Host Name . . . . . . . . . . . . :
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 2C-60-0C-9B-A8-89
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter PoĄczenie lokalne* 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : AE-E0-10-65-58-B9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Karta sieciowa Broadcom 802.11n
Physical Address. . . . . . . . . : AC-E0-10-65-58-B9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::fc42:138f:fb5a:f6ff%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.172(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 21 grudnia 2015 22:16:55
Lease Expires . . . . . . . . . . : 28 grudnia 2015 22:21:43
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 217.172.224.160
192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{9E3DA69D-E183-4041-9944-35B59277B529}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Setting DNS to 8.8.8.8 doesn't work, see replies to suggestions beneath.
It doesn't resolve local hostnames either. The machine doesn't respond to pings from local network.
Any ideas how to proceed? Help my dad enjoy his internet!
networking windows-10 dns ip ping
add a comment |
Facts:
- The browser doesn't load any pages, whether they are addressed with IP or hostname.
ping google.com
doesn't work, returningPing request could not find host google.com.
ping 216.58.209.78
(google IP) does work, sending and receiving all packets.
nslookup google.com
does work, returning correct IP address that then does indeed work withping
.- Network settings are default, IP and DNS are set to auto.
- Specifying OpenDNS in network settings does not help.
- There are no entries in
c:windowssystem32driversetchost
- There are no DNS prefixes in use.
netsh winsock reset & netsh int ip reset
does not help.- DNS client is running.
- The most common given solution on the Internet
ipconfig /flushdns & ipconfig /registerdns
does not work, with latter returningRegistration of DNS records failed: Parameter is not correct.
It happens occassionally to people, but I have not found possible solutions to this problem. I sense this might be the key to my ordeal. - All of the above happens for different networks.
- The PC has been recently formatted. One guy had the same problem and it helped to restore the previous PC name, but I have no way of finding what the name was before the format.
ipconfig /all
is as below. The first paragraph looks a bit blank, perhaps something there...?
Windows IP Configuration
Host Name . . . . . . . . . . . . :
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 2C-60-0C-9B-A8-89
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter PoĄczenie lokalne* 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : AE-E0-10-65-58-B9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Karta sieciowa Broadcom 802.11n
Physical Address. . . . . . . . . : AC-E0-10-65-58-B9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::fc42:138f:fb5a:f6ff%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.172(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 21 grudnia 2015 22:16:55
Lease Expires . . . . . . . . . . : 28 grudnia 2015 22:21:43
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 217.172.224.160
192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{9E3DA69D-E183-4041-9944-35B59277B529}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Setting DNS to 8.8.8.8 doesn't work, see replies to suggestions beneath.
It doesn't resolve local hostnames either. The machine doesn't respond to pings from local network.
Any ideas how to proceed? Help my dad enjoy his internet!
networking windows-10 dns ip ping
Is static IP and DNS working? From where are you getting DHCP info? Can you check you DHCP server configuration?
– g2mk
Dec 29 '15 at 21:31
If 192.168.0.1 is your router then try to remove 192.168.0.1 from its DNS servers... I guess that 217.172.224.160 is valid DNS server and just rejects external requests. Have you tried setup OpenDNS on your DHCP server?
– g2mk
Dec 29 '15 at 21:57
Hi, g2mk. OP here. I tried to follow your line of thought with some google-fu. Static IP and DNS do not work, I can tell that for sure. As for DHCP, I'm not sure how to reply to these questions. It is a standard and public-available DSL service supplied by one of the local Internet providers. Is DHCP on my side of things, or is it theirs? I tried following blogs.catapultsystems.com/jcwarner/archive/2011/06/27/… to get some info on my DHCP, but it doesn't recognizeshow server
command. I'm not sure how to proceed.
– user2551153
Jan 4 '16 at 17:01
add a comment |
Facts:
- The browser doesn't load any pages, whether they are addressed with IP or hostname.
ping google.com
doesn't work, returningPing request could not find host google.com.
ping 216.58.209.78
(google IP) does work, sending and receiving all packets.
nslookup google.com
does work, returning correct IP address that then does indeed work withping
.- Network settings are default, IP and DNS are set to auto.
- Specifying OpenDNS in network settings does not help.
- There are no entries in
c:windowssystem32driversetchost
- There are no DNS prefixes in use.
netsh winsock reset & netsh int ip reset
does not help.- DNS client is running.
- The most common given solution on the Internet
ipconfig /flushdns & ipconfig /registerdns
does not work, with latter returningRegistration of DNS records failed: Parameter is not correct.
It happens occassionally to people, but I have not found possible solutions to this problem. I sense this might be the key to my ordeal. - All of the above happens for different networks.
- The PC has been recently formatted. One guy had the same problem and it helped to restore the previous PC name, but I have no way of finding what the name was before the format.
ipconfig /all
is as below. The first paragraph looks a bit blank, perhaps something there...?
Windows IP Configuration
Host Name . . . . . . . . . . . . :
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 2C-60-0C-9B-A8-89
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter PoĄczenie lokalne* 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : AE-E0-10-65-58-B9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Karta sieciowa Broadcom 802.11n
Physical Address. . . . . . . . . : AC-E0-10-65-58-B9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::fc42:138f:fb5a:f6ff%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.172(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 21 grudnia 2015 22:16:55
Lease Expires . . . . . . . . . . : 28 grudnia 2015 22:21:43
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 217.172.224.160
192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{9E3DA69D-E183-4041-9944-35B59277B529}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Setting DNS to 8.8.8.8 doesn't work, see replies to suggestions beneath.
It doesn't resolve local hostnames either. The machine doesn't respond to pings from local network.
Any ideas how to proceed? Help my dad enjoy his internet!
networking windows-10 dns ip ping
Facts:
- The browser doesn't load any pages, whether they are addressed with IP or hostname.
ping google.com
doesn't work, returningPing request could not find host google.com.
ping 216.58.209.78
(google IP) does work, sending and receiving all packets.
nslookup google.com
does work, returning correct IP address that then does indeed work withping
.- Network settings are default, IP and DNS are set to auto.
- Specifying OpenDNS in network settings does not help.
- There are no entries in
c:windowssystem32driversetchost
- There are no DNS prefixes in use.
netsh winsock reset & netsh int ip reset
does not help.- DNS client is running.
- The most common given solution on the Internet
ipconfig /flushdns & ipconfig /registerdns
does not work, with latter returningRegistration of DNS records failed: Parameter is not correct.
It happens occassionally to people, but I have not found possible solutions to this problem. I sense this might be the key to my ordeal. - All of the above happens for different networks.
- The PC has been recently formatted. One guy had the same problem and it helped to restore the previous PC name, but I have no way of finding what the name was before the format.
ipconfig /all
is as below. The first paragraph looks a bit blank, perhaps something there...?
Windows IP Configuration
Host Name . . . . . . . . . . . . :
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Ethernet adapter Ethernet:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller
Physical Address. . . . . . . . . : 2C-60-0C-9B-A8-89
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter PoĄczenie lokalne* 2:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : AE-E0-10-65-58-B9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Karta sieciowa Broadcom 802.11n
Physical Address. . . . . . . . . : AC-E0-10-65-58-B9
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::fc42:138f:fb5a:f6ff%12(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.0.172(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 21 grudnia 2015 22:16:55
Lease Expires . . . . . . . . . . : 28 grudnia 2015 22:21:43
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 217.172.224.160
192.168.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Tunnel adapter isatap.{9E3DA69D-E183-4041-9944-35B59277B529}:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft ISATAP Adapter
Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Setting DNS to 8.8.8.8 doesn't work, see replies to suggestions beneath.
It doesn't resolve local hostnames either. The machine doesn't respond to pings from local network.
Any ideas how to proceed? Help my dad enjoy his internet!
networking windows-10 dns ip ping
networking windows-10 dns ip ping
edited Jun 17 '16 at 9:00
Donal Fellows
22516
22516
asked Dec 29 '15 at 21:03
user2551153
46116
46116
Is static IP and DNS working? From where are you getting DHCP info? Can you check you DHCP server configuration?
– g2mk
Dec 29 '15 at 21:31
If 192.168.0.1 is your router then try to remove 192.168.0.1 from its DNS servers... I guess that 217.172.224.160 is valid DNS server and just rejects external requests. Have you tried setup OpenDNS on your DHCP server?
– g2mk
Dec 29 '15 at 21:57
Hi, g2mk. OP here. I tried to follow your line of thought with some google-fu. Static IP and DNS do not work, I can tell that for sure. As for DHCP, I'm not sure how to reply to these questions. It is a standard and public-available DSL service supplied by one of the local Internet providers. Is DHCP on my side of things, or is it theirs? I tried following blogs.catapultsystems.com/jcwarner/archive/2011/06/27/… to get some info on my DHCP, but it doesn't recognizeshow server
command. I'm not sure how to proceed.
– user2551153
Jan 4 '16 at 17:01
add a comment |
Is static IP and DNS working? From where are you getting DHCP info? Can you check you DHCP server configuration?
– g2mk
Dec 29 '15 at 21:31
If 192.168.0.1 is your router then try to remove 192.168.0.1 from its DNS servers... I guess that 217.172.224.160 is valid DNS server and just rejects external requests. Have you tried setup OpenDNS on your DHCP server?
– g2mk
Dec 29 '15 at 21:57
Hi, g2mk. OP here. I tried to follow your line of thought with some google-fu. Static IP and DNS do not work, I can tell that for sure. As for DHCP, I'm not sure how to reply to these questions. It is a standard and public-available DSL service supplied by one of the local Internet providers. Is DHCP on my side of things, or is it theirs? I tried following blogs.catapultsystems.com/jcwarner/archive/2011/06/27/… to get some info on my DHCP, but it doesn't recognizeshow server
command. I'm not sure how to proceed.
– user2551153
Jan 4 '16 at 17:01
Is static IP and DNS working? From where are you getting DHCP info? Can you check you DHCP server configuration?
– g2mk
Dec 29 '15 at 21:31
Is static IP and DNS working? From where are you getting DHCP info? Can you check you DHCP server configuration?
– g2mk
Dec 29 '15 at 21:31
If 192.168.0.1 is your router then try to remove 192.168.0.1 from its DNS servers... I guess that 217.172.224.160 is valid DNS server and just rejects external requests. Have you tried setup OpenDNS on your DHCP server?
– g2mk
Dec 29 '15 at 21:57
If 192.168.0.1 is your router then try to remove 192.168.0.1 from its DNS servers... I guess that 217.172.224.160 is valid DNS server and just rejects external requests. Have you tried setup OpenDNS on your DHCP server?
– g2mk
Dec 29 '15 at 21:57
Hi, g2mk. OP here. I tried to follow your line of thought with some google-fu. Static IP and DNS do not work, I can tell that for sure. As for DHCP, I'm not sure how to reply to these questions. It is a standard and public-available DSL service supplied by one of the local Internet providers. Is DHCP on my side of things, or is it theirs? I tried following blogs.catapultsystems.com/jcwarner/archive/2011/06/27/… to get some info on my DHCP, but it doesn't recognize
show server
command. I'm not sure how to proceed.– user2551153
Jan 4 '16 at 17:01
Hi, g2mk. OP here. I tried to follow your line of thought with some google-fu. Static IP and DNS do not work, I can tell that for sure. As for DHCP, I'm not sure how to reply to these questions. It is a standard and public-available DSL service supplied by one of the local Internet providers. Is DHCP on my side of things, or is it theirs? I tried following blogs.catapultsystems.com/jcwarner/archive/2011/06/27/… to get some info on my DHCP, but it doesn't recognize
show server
command. I'm not sure how to proceed.– user2551153
Jan 4 '16 at 17:01
add a comment |
10 Answers
10
active
oldest
votes
a. You can try to manually set the dns servers to the google ones: 8.8.8.8
and 8.8.4.4
b. You can try another wireless adapter
c. You can try a linux live cd and verify if the issues are still present
a. It didn't work. See my other replies for more detail. b. It didn't work with another wireless adapter and ethernet cable.
– user2551153
Jan 4 '16 at 16:54
@user2551153 please try a linux live cd/usb (using the wired connection if possible), since your issue is strange enough to make me think of viruses/firewalls/group policy settings.
– alexandrul
Jan 4 '16 at 20:57
add a comment |
In my case, I have hyper-v manager installed and has one virtual switch that bridges my NIC with it. Try disabling/removing the virtual switch in hyper-v manager (elevated user needed). This one works for me. Maybe Windows 10 or hyper-v has a buggy virtual switch.
add a comment |
I've had these symptoms two or three times in the past after installing a new NIC or router, using WinXP and Win7. Solutions varied, but in one case the issue was resolved by unticking the "use NetBIOS over TCP" box. In the other case I remember having to run some unusual command line utility (not ipconfig /flushdns; something else that I don't quite recall) to flush cached somethingsomethingsomething.
One thing I'd check is whether local (LAN side) hostnames resolve ok. If it's only WAN side hostnames that don't resolve properly then at least you know the problem is not on your PC.
Hi. I tried playing with 'use NetBIOS over TCP'. I don't know which unusual command line utility you refer to, but google often points tonbtstat -R
ornbtstat -RR
in this case. I tried each and it didn't change a thing. I also tried to restart the computer (does that clear the cache you refer to? I don't know. But just in case...). It doesn't resolve local hostnames either. On an interesting side-note : it doesn't respond to local pings either.
– user2551153
Jan 4 '16 at 16:48
add a comment |
DNS issue. DHCP is not a possible culprit. Did you try setting the DNS to 8.8.8.8? Don't forget to flush the dnscache between changes.
Hi, Dr. Ping. Thanks for your input. I did try setting DNS to 8.8.8.8. When IPv4 DNS is set to 8.8.8.8 and IPv6 is set to auto, it works like this:nslookup google.com Server: google-public-dns.a.google.com Address: 8.8.8.8 Non authoritative answer: Name: google.com Addresses: 2a00:1450:401 :801:200e 216.58.209.46
which I suppose is okay. When I set IPv4 to 8.8.8.8 and similarly IPv6 to 2001:4860:4860::8888 (IPv6 of google DNS) it works like thisnslookup google.com Server: UnKnown Address: 2001:.... *** UnKnown can't find google.com: No response from server
. IPv6 can't be set to 8.8.8.8
– user2551153
Jan 4 '16 at 16:21
2/2 ... And when I set IPv4 to 8.8.8.8 and disable IPv6 altogether, it works the same as when IPv6 is set to auto.ping google.com
doesn't work in any of these cases.
– user2551153
Jan 4 '16 at 16:22
add a comment |
You indicate that nslookup works. What is the name of the DNS server being queried? That may provide you with some hint as to where your system is getting it's information and allow you to make corrections...if it does not match your expected output.
Jeremys-iMac:~ jeremy$ nslookup google.com
Server: 2001:4860:4860::8888
Address: 2001:4860:4860::8888#53
Non-authoritative answer:
Name: google.com
Address: 216.58.216.14
Hi, Jeremy. Thanks for your input. I did try setting DNS to 8.8.8.8. When IPv4 DNS is set to 8.8.8.8 and IPv6 is set to auto, it works like this:nslookup google.com Server: google-public-dns.a.google.com Address: 8.8.8.8 Non authoritative answer: Name: google.com Addresses: 2a00:1450:401 :801:200e 216.58.209.46
which I suppose is okay. When I set IPv4 to 8.8.8.8 and similarly IPv6 to 2001:4860:4860::8888 (IPv6 of google DNS) it works like thisnslookup google.com Server: UnKnown Address: 2001:.... *** UnKnown can't find google.com: No response from server.
IPv6 can't be set to 8.8.8.8
– user2551153
Jan 4 '16 at 16:23
2/2 ... And when I set IPv4 to 8.8.8.8 and disable IPv6 altogether, it works the same as when IPv6 is set to auto.ping google.com
doesn't work in any of these cases.
– user2551153
Jan 4 '16 at 16:24
add a comment |
The fact that the computer was recently reformatted could indicate a problem with the drivers for your network adapter(s).
Open "View network connections" and try disabling each adapter one-by-one. After disabling each one, test the DNS and then re-enable it. Perhaps you'll find one that's causing your DNS problems - if you do, you could try reinstalling the driver for that particular adapter.
It has to be a DNS problem. If you can ping the IP but it doesn't resolve, that's got to be the issue.
– user1780242
Dec 30 '15 at 2:35
Agreed, but DNS goes through the network adapter. It's entirely possible that the driver for the network adapter has a bug that's interfering with DNS. I was particularly suspicious of the "Microsoft Wi-Fi Direct Virtual Adapter" in your ipconfig dump. It's Microsoft-made, but I'm not clear on what it actually does.
– LevenTech
Dec 30 '15 at 4:16
Hi, man. OP here. I tried doing as you said, but all entries I see under 'view network connections' are: Ethernet (Realtek PCIe GBE Family Controller) and Wi-Fi (Network card Broadcom 802.11n). There was no Microsoft Wi-Fi Direct Virtual Adapter or anything else. I disabled / re-enabled both of them : the first one didn't really change a thing, and the second one was wi-fi so there was no connection whatsoever. I also tried following steps on windows.microsoft.com/en-us/windows/… but it produced same results.
– user2551153
Jan 4 '16 at 16:32
add a comment |
I just came across this same issue on a Windows 10 Dell tablet that one of my users brought into the office. Same issue, communications via IP work, but name resolution not working (aside from nslookup, oddly that was working fine).
After digging into this for a few minutes I also discovered that the tablet was missing a hostname entry when doing an ipconfig /all (same as shown in your screenshot above), so I went into the System properties and found that there was no computer name set in there. Added a computer name, rebooted, et voila! Name resolution is now working properly.
add a comment |
I had the same issue (probably after a heat crash). Took me hours to figure out that the HOSTNAME of the machine was deleted. Reentered it (including primary DNS-domain and workgroup name) and everything runs fine again. Good luck!
add a comment |
All the things suggested by other posters failed, so I resorted to drastic measures and did a full format with a fresh Win 10 install. It did work.
8
That's like "healing the disease by killing the patient". This shouldn't be the accepted answer.
– Fábio Antunes
Nov 27 '16 at 14:38
I agree. It's just that none of the suggestions worked and I did check each of them diligently. I'm sorry we couldn't reach a fruitful conclusion.
– user2551153
Mar 22 '17 at 13:49
add a comment |
The answer is in the first section of the ipconfig
.
Windows IP Configuration
Host Name . . . . . . . . . . . . :
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Host name is blank.
Set the computer name in Control PanelSystem and SecuritySystem, and all will be well.
New contributor
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1019467%2fwindows-10-cant-resolve-hostnames-ping-with-ip-works-but-not-with-hostname%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
10 Answers
10
active
oldest
votes
10 Answers
10
active
oldest
votes
active
oldest
votes
active
oldest
votes
a. You can try to manually set the dns servers to the google ones: 8.8.8.8
and 8.8.4.4
b. You can try another wireless adapter
c. You can try a linux live cd and verify if the issues are still present
a. It didn't work. See my other replies for more detail. b. It didn't work with another wireless adapter and ethernet cable.
– user2551153
Jan 4 '16 at 16:54
@user2551153 please try a linux live cd/usb (using the wired connection if possible), since your issue is strange enough to make me think of viruses/firewalls/group policy settings.
– alexandrul
Jan 4 '16 at 20:57
add a comment |
a. You can try to manually set the dns servers to the google ones: 8.8.8.8
and 8.8.4.4
b. You can try another wireless adapter
c. You can try a linux live cd and verify if the issues are still present
a. It didn't work. See my other replies for more detail. b. It didn't work with another wireless adapter and ethernet cable.
– user2551153
Jan 4 '16 at 16:54
@user2551153 please try a linux live cd/usb (using the wired connection if possible), since your issue is strange enough to make me think of viruses/firewalls/group policy settings.
– alexandrul
Jan 4 '16 at 20:57
add a comment |
a. You can try to manually set the dns servers to the google ones: 8.8.8.8
and 8.8.4.4
b. You can try another wireless adapter
c. You can try a linux live cd and verify if the issues are still present
a. You can try to manually set the dns servers to the google ones: 8.8.8.8
and 8.8.4.4
b. You can try another wireless adapter
c. You can try a linux live cd and verify if the issues are still present
answered Dec 29 '15 at 21:20
alexandrul
9151520
9151520
a. It didn't work. See my other replies for more detail. b. It didn't work with another wireless adapter and ethernet cable.
– user2551153
Jan 4 '16 at 16:54
@user2551153 please try a linux live cd/usb (using the wired connection if possible), since your issue is strange enough to make me think of viruses/firewalls/group policy settings.
– alexandrul
Jan 4 '16 at 20:57
add a comment |
a. It didn't work. See my other replies for more detail. b. It didn't work with another wireless adapter and ethernet cable.
– user2551153
Jan 4 '16 at 16:54
@user2551153 please try a linux live cd/usb (using the wired connection if possible), since your issue is strange enough to make me think of viruses/firewalls/group policy settings.
– alexandrul
Jan 4 '16 at 20:57
a. It didn't work. See my other replies for more detail. b. It didn't work with another wireless adapter and ethernet cable.
– user2551153
Jan 4 '16 at 16:54
a. It didn't work. See my other replies for more detail. b. It didn't work with another wireless adapter and ethernet cable.
– user2551153
Jan 4 '16 at 16:54
@user2551153 please try a linux live cd/usb (using the wired connection if possible), since your issue is strange enough to make me think of viruses/firewalls/group policy settings.
– alexandrul
Jan 4 '16 at 20:57
@user2551153 please try a linux live cd/usb (using the wired connection if possible), since your issue is strange enough to make me think of viruses/firewalls/group policy settings.
– alexandrul
Jan 4 '16 at 20:57
add a comment |
In my case, I have hyper-v manager installed and has one virtual switch that bridges my NIC with it. Try disabling/removing the virtual switch in hyper-v manager (elevated user needed). This one works for me. Maybe Windows 10 or hyper-v has a buggy virtual switch.
add a comment |
In my case, I have hyper-v manager installed and has one virtual switch that bridges my NIC with it. Try disabling/removing the virtual switch in hyper-v manager (elevated user needed). This one works for me. Maybe Windows 10 or hyper-v has a buggy virtual switch.
add a comment |
In my case, I have hyper-v manager installed and has one virtual switch that bridges my NIC with it. Try disabling/removing the virtual switch in hyper-v manager (elevated user needed). This one works for me. Maybe Windows 10 or hyper-v has a buggy virtual switch.
In my case, I have hyper-v manager installed and has one virtual switch that bridges my NIC with it. Try disabling/removing the virtual switch in hyper-v manager (elevated user needed). This one works for me. Maybe Windows 10 or hyper-v has a buggy virtual switch.
answered Mar 24 '17 at 16:05
karlo
111
111
add a comment |
add a comment |
I've had these symptoms two or three times in the past after installing a new NIC or router, using WinXP and Win7. Solutions varied, but in one case the issue was resolved by unticking the "use NetBIOS over TCP" box. In the other case I remember having to run some unusual command line utility (not ipconfig /flushdns; something else that I don't quite recall) to flush cached somethingsomethingsomething.
One thing I'd check is whether local (LAN side) hostnames resolve ok. If it's only WAN side hostnames that don't resolve properly then at least you know the problem is not on your PC.
Hi. I tried playing with 'use NetBIOS over TCP'. I don't know which unusual command line utility you refer to, but google often points tonbtstat -R
ornbtstat -RR
in this case. I tried each and it didn't change a thing. I also tried to restart the computer (does that clear the cache you refer to? I don't know. But just in case...). It doesn't resolve local hostnames either. On an interesting side-note : it doesn't respond to local pings either.
– user2551153
Jan 4 '16 at 16:48
add a comment |
I've had these symptoms two or three times in the past after installing a new NIC or router, using WinXP and Win7. Solutions varied, but in one case the issue was resolved by unticking the "use NetBIOS over TCP" box. In the other case I remember having to run some unusual command line utility (not ipconfig /flushdns; something else that I don't quite recall) to flush cached somethingsomethingsomething.
One thing I'd check is whether local (LAN side) hostnames resolve ok. If it's only WAN side hostnames that don't resolve properly then at least you know the problem is not on your PC.
Hi. I tried playing with 'use NetBIOS over TCP'. I don't know which unusual command line utility you refer to, but google often points tonbtstat -R
ornbtstat -RR
in this case. I tried each and it didn't change a thing. I also tried to restart the computer (does that clear the cache you refer to? I don't know. But just in case...). It doesn't resolve local hostnames either. On an interesting side-note : it doesn't respond to local pings either.
– user2551153
Jan 4 '16 at 16:48
add a comment |
I've had these symptoms two or three times in the past after installing a new NIC or router, using WinXP and Win7. Solutions varied, but in one case the issue was resolved by unticking the "use NetBIOS over TCP" box. In the other case I remember having to run some unusual command line utility (not ipconfig /flushdns; something else that I don't quite recall) to flush cached somethingsomethingsomething.
One thing I'd check is whether local (LAN side) hostnames resolve ok. If it's only WAN side hostnames that don't resolve properly then at least you know the problem is not on your PC.
I've had these symptoms two or three times in the past after installing a new NIC or router, using WinXP and Win7. Solutions varied, but in one case the issue was resolved by unticking the "use NetBIOS over TCP" box. In the other case I remember having to run some unusual command line utility (not ipconfig /flushdns; something else that I don't quite recall) to flush cached somethingsomethingsomething.
One thing I'd check is whether local (LAN side) hostnames resolve ok. If it's only WAN side hostnames that don't resolve properly then at least you know the problem is not on your PC.
answered Dec 29 '15 at 21:40
HamishKL
101
101
Hi. I tried playing with 'use NetBIOS over TCP'. I don't know which unusual command line utility you refer to, but google often points tonbtstat -R
ornbtstat -RR
in this case. I tried each and it didn't change a thing. I also tried to restart the computer (does that clear the cache you refer to? I don't know. But just in case...). It doesn't resolve local hostnames either. On an interesting side-note : it doesn't respond to local pings either.
– user2551153
Jan 4 '16 at 16:48
add a comment |
Hi. I tried playing with 'use NetBIOS over TCP'. I don't know which unusual command line utility you refer to, but google often points tonbtstat -R
ornbtstat -RR
in this case. I tried each and it didn't change a thing. I also tried to restart the computer (does that clear the cache you refer to? I don't know. But just in case...). It doesn't resolve local hostnames either. On an interesting side-note : it doesn't respond to local pings either.
– user2551153
Jan 4 '16 at 16:48
Hi. I tried playing with 'use NetBIOS over TCP'. I don't know which unusual command line utility you refer to, but google often points to
nbtstat -R
or nbtstat -RR
in this case. I tried each and it didn't change a thing. I also tried to restart the computer (does that clear the cache you refer to? I don't know. But just in case...). It doesn't resolve local hostnames either. On an interesting side-note : it doesn't respond to local pings either.– user2551153
Jan 4 '16 at 16:48
Hi. I tried playing with 'use NetBIOS over TCP'. I don't know which unusual command line utility you refer to, but google often points to
nbtstat -R
or nbtstat -RR
in this case. I tried each and it didn't change a thing. I also tried to restart the computer (does that clear the cache you refer to? I don't know. But just in case...). It doesn't resolve local hostnames either. On an interesting side-note : it doesn't respond to local pings either.– user2551153
Jan 4 '16 at 16:48
add a comment |
DNS issue. DHCP is not a possible culprit. Did you try setting the DNS to 8.8.8.8? Don't forget to flush the dnscache between changes.
Hi, Dr. Ping. Thanks for your input. I did try setting DNS to 8.8.8.8. When IPv4 DNS is set to 8.8.8.8 and IPv6 is set to auto, it works like this:nslookup google.com Server: google-public-dns.a.google.com Address: 8.8.8.8 Non authoritative answer: Name: google.com Addresses: 2a00:1450:401 :801:200e 216.58.209.46
which I suppose is okay. When I set IPv4 to 8.8.8.8 and similarly IPv6 to 2001:4860:4860::8888 (IPv6 of google DNS) it works like thisnslookup google.com Server: UnKnown Address: 2001:.... *** UnKnown can't find google.com: No response from server
. IPv6 can't be set to 8.8.8.8
– user2551153
Jan 4 '16 at 16:21
2/2 ... And when I set IPv4 to 8.8.8.8 and disable IPv6 altogether, it works the same as when IPv6 is set to auto.ping google.com
doesn't work in any of these cases.
– user2551153
Jan 4 '16 at 16:22
add a comment |
DNS issue. DHCP is not a possible culprit. Did you try setting the DNS to 8.8.8.8? Don't forget to flush the dnscache between changes.
Hi, Dr. Ping. Thanks for your input. I did try setting DNS to 8.8.8.8. When IPv4 DNS is set to 8.8.8.8 and IPv6 is set to auto, it works like this:nslookup google.com Server: google-public-dns.a.google.com Address: 8.8.8.8 Non authoritative answer: Name: google.com Addresses: 2a00:1450:401 :801:200e 216.58.209.46
which I suppose is okay. When I set IPv4 to 8.8.8.8 and similarly IPv6 to 2001:4860:4860::8888 (IPv6 of google DNS) it works like thisnslookup google.com Server: UnKnown Address: 2001:.... *** UnKnown can't find google.com: No response from server
. IPv6 can't be set to 8.8.8.8
– user2551153
Jan 4 '16 at 16:21
2/2 ... And when I set IPv4 to 8.8.8.8 and disable IPv6 altogether, it works the same as when IPv6 is set to auto.ping google.com
doesn't work in any of these cases.
– user2551153
Jan 4 '16 at 16:22
add a comment |
DNS issue. DHCP is not a possible culprit. Did you try setting the DNS to 8.8.8.8? Don't forget to flush the dnscache between changes.
DNS issue. DHCP is not a possible culprit. Did you try setting the DNS to 8.8.8.8? Don't forget to flush the dnscache between changes.
answered Dec 29 '15 at 22:54
Dr.Ping
1098
1098
Hi, Dr. Ping. Thanks for your input. I did try setting DNS to 8.8.8.8. When IPv4 DNS is set to 8.8.8.8 and IPv6 is set to auto, it works like this:nslookup google.com Server: google-public-dns.a.google.com Address: 8.8.8.8 Non authoritative answer: Name: google.com Addresses: 2a00:1450:401 :801:200e 216.58.209.46
which I suppose is okay. When I set IPv4 to 8.8.8.8 and similarly IPv6 to 2001:4860:4860::8888 (IPv6 of google DNS) it works like thisnslookup google.com Server: UnKnown Address: 2001:.... *** UnKnown can't find google.com: No response from server
. IPv6 can't be set to 8.8.8.8
– user2551153
Jan 4 '16 at 16:21
2/2 ... And when I set IPv4 to 8.8.8.8 and disable IPv6 altogether, it works the same as when IPv6 is set to auto.ping google.com
doesn't work in any of these cases.
– user2551153
Jan 4 '16 at 16:22
add a comment |
Hi, Dr. Ping. Thanks for your input. I did try setting DNS to 8.8.8.8. When IPv4 DNS is set to 8.8.8.8 and IPv6 is set to auto, it works like this:nslookup google.com Server: google-public-dns.a.google.com Address: 8.8.8.8 Non authoritative answer: Name: google.com Addresses: 2a00:1450:401 :801:200e 216.58.209.46
which I suppose is okay. When I set IPv4 to 8.8.8.8 and similarly IPv6 to 2001:4860:4860::8888 (IPv6 of google DNS) it works like thisnslookup google.com Server: UnKnown Address: 2001:.... *** UnKnown can't find google.com: No response from server
. IPv6 can't be set to 8.8.8.8
– user2551153
Jan 4 '16 at 16:21
2/2 ... And when I set IPv4 to 8.8.8.8 and disable IPv6 altogether, it works the same as when IPv6 is set to auto.ping google.com
doesn't work in any of these cases.
– user2551153
Jan 4 '16 at 16:22
Hi, Dr. Ping. Thanks for your input. I did try setting DNS to 8.8.8.8. When IPv4 DNS is set to 8.8.8.8 and IPv6 is set to auto, it works like this:
nslookup google.com Server: google-public-dns.a.google.com Address: 8.8.8.8 Non authoritative answer: Name: google.com Addresses: 2a00:1450:401 :801:200e 216.58.209.46
which I suppose is okay. When I set IPv4 to 8.8.8.8 and similarly IPv6 to 2001:4860:4860::8888 (IPv6 of google DNS) it works like this nslookup google.com Server: UnKnown Address: 2001:.... *** UnKnown can't find google.com: No response from server
. IPv6 can't be set to 8.8.8.8– user2551153
Jan 4 '16 at 16:21
Hi, Dr. Ping. Thanks for your input. I did try setting DNS to 8.8.8.8. When IPv4 DNS is set to 8.8.8.8 and IPv6 is set to auto, it works like this:
nslookup google.com Server: google-public-dns.a.google.com Address: 8.8.8.8 Non authoritative answer: Name: google.com Addresses: 2a00:1450:401 :801:200e 216.58.209.46
which I suppose is okay. When I set IPv4 to 8.8.8.8 and similarly IPv6 to 2001:4860:4860::8888 (IPv6 of google DNS) it works like this nslookup google.com Server: UnKnown Address: 2001:.... *** UnKnown can't find google.com: No response from server
. IPv6 can't be set to 8.8.8.8– user2551153
Jan 4 '16 at 16:21
2/2 ... And when I set IPv4 to 8.8.8.8 and disable IPv6 altogether, it works the same as when IPv6 is set to auto.
ping google.com
doesn't work in any of these cases.– user2551153
Jan 4 '16 at 16:22
2/2 ... And when I set IPv4 to 8.8.8.8 and disable IPv6 altogether, it works the same as when IPv6 is set to auto.
ping google.com
doesn't work in any of these cases.– user2551153
Jan 4 '16 at 16:22
add a comment |
You indicate that nslookup works. What is the name of the DNS server being queried? That may provide you with some hint as to where your system is getting it's information and allow you to make corrections...if it does not match your expected output.
Jeremys-iMac:~ jeremy$ nslookup google.com
Server: 2001:4860:4860::8888
Address: 2001:4860:4860::8888#53
Non-authoritative answer:
Name: google.com
Address: 216.58.216.14
Hi, Jeremy. Thanks for your input. I did try setting DNS to 8.8.8.8. When IPv4 DNS is set to 8.8.8.8 and IPv6 is set to auto, it works like this:nslookup google.com Server: google-public-dns.a.google.com Address: 8.8.8.8 Non authoritative answer: Name: google.com Addresses: 2a00:1450:401 :801:200e 216.58.209.46
which I suppose is okay. When I set IPv4 to 8.8.8.8 and similarly IPv6 to 2001:4860:4860::8888 (IPv6 of google DNS) it works like thisnslookup google.com Server: UnKnown Address: 2001:.... *** UnKnown can't find google.com: No response from server.
IPv6 can't be set to 8.8.8.8
– user2551153
Jan 4 '16 at 16:23
2/2 ... And when I set IPv4 to 8.8.8.8 and disable IPv6 altogether, it works the same as when IPv6 is set to auto.ping google.com
doesn't work in any of these cases.
– user2551153
Jan 4 '16 at 16:24
add a comment |
You indicate that nslookup works. What is the name of the DNS server being queried? That may provide you with some hint as to where your system is getting it's information and allow you to make corrections...if it does not match your expected output.
Jeremys-iMac:~ jeremy$ nslookup google.com
Server: 2001:4860:4860::8888
Address: 2001:4860:4860::8888#53
Non-authoritative answer:
Name: google.com
Address: 216.58.216.14
Hi, Jeremy. Thanks for your input. I did try setting DNS to 8.8.8.8. When IPv4 DNS is set to 8.8.8.8 and IPv6 is set to auto, it works like this:nslookup google.com Server: google-public-dns.a.google.com Address: 8.8.8.8 Non authoritative answer: Name: google.com Addresses: 2a00:1450:401 :801:200e 216.58.209.46
which I suppose is okay. When I set IPv4 to 8.8.8.8 and similarly IPv6 to 2001:4860:4860::8888 (IPv6 of google DNS) it works like thisnslookup google.com Server: UnKnown Address: 2001:.... *** UnKnown can't find google.com: No response from server.
IPv6 can't be set to 8.8.8.8
– user2551153
Jan 4 '16 at 16:23
2/2 ... And when I set IPv4 to 8.8.8.8 and disable IPv6 altogether, it works the same as when IPv6 is set to auto.ping google.com
doesn't work in any of these cases.
– user2551153
Jan 4 '16 at 16:24
add a comment |
You indicate that nslookup works. What is the name of the DNS server being queried? That may provide you with some hint as to where your system is getting it's information and allow you to make corrections...if it does not match your expected output.
Jeremys-iMac:~ jeremy$ nslookup google.com
Server: 2001:4860:4860::8888
Address: 2001:4860:4860::8888#53
Non-authoritative answer:
Name: google.com
Address: 216.58.216.14
You indicate that nslookup works. What is the name of the DNS server being queried? That may provide you with some hint as to where your system is getting it's information and allow you to make corrections...if it does not match your expected output.
Jeremys-iMac:~ jeremy$ nslookup google.com
Server: 2001:4860:4860::8888
Address: 2001:4860:4860::8888#53
Non-authoritative answer:
Name: google.com
Address: 216.58.216.14
answered Dec 30 '15 at 1:07
Jeremy J Einsweiler
111
111
Hi, Jeremy. Thanks for your input. I did try setting DNS to 8.8.8.8. When IPv4 DNS is set to 8.8.8.8 and IPv6 is set to auto, it works like this:nslookup google.com Server: google-public-dns.a.google.com Address: 8.8.8.8 Non authoritative answer: Name: google.com Addresses: 2a00:1450:401 :801:200e 216.58.209.46
which I suppose is okay. When I set IPv4 to 8.8.8.8 and similarly IPv6 to 2001:4860:4860::8888 (IPv6 of google DNS) it works like thisnslookup google.com Server: UnKnown Address: 2001:.... *** UnKnown can't find google.com: No response from server.
IPv6 can't be set to 8.8.8.8
– user2551153
Jan 4 '16 at 16:23
2/2 ... And when I set IPv4 to 8.8.8.8 and disable IPv6 altogether, it works the same as when IPv6 is set to auto.ping google.com
doesn't work in any of these cases.
– user2551153
Jan 4 '16 at 16:24
add a comment |
Hi, Jeremy. Thanks for your input. I did try setting DNS to 8.8.8.8. When IPv4 DNS is set to 8.8.8.8 and IPv6 is set to auto, it works like this:nslookup google.com Server: google-public-dns.a.google.com Address: 8.8.8.8 Non authoritative answer: Name: google.com Addresses: 2a00:1450:401 :801:200e 216.58.209.46
which I suppose is okay. When I set IPv4 to 8.8.8.8 and similarly IPv6 to 2001:4860:4860::8888 (IPv6 of google DNS) it works like thisnslookup google.com Server: UnKnown Address: 2001:.... *** UnKnown can't find google.com: No response from server.
IPv6 can't be set to 8.8.8.8
– user2551153
Jan 4 '16 at 16:23
2/2 ... And when I set IPv4 to 8.8.8.8 and disable IPv6 altogether, it works the same as when IPv6 is set to auto.ping google.com
doesn't work in any of these cases.
– user2551153
Jan 4 '16 at 16:24
Hi, Jeremy. Thanks for your input. I did try setting DNS to 8.8.8.8. When IPv4 DNS is set to 8.8.8.8 and IPv6 is set to auto, it works like this:
nslookup google.com Server: google-public-dns.a.google.com Address: 8.8.8.8 Non authoritative answer: Name: google.com Addresses: 2a00:1450:401 :801:200e 216.58.209.46
which I suppose is okay. When I set IPv4 to 8.8.8.8 and similarly IPv6 to 2001:4860:4860::8888 (IPv6 of google DNS) it works like this nslookup google.com Server: UnKnown Address: 2001:.... *** UnKnown can't find google.com: No response from server.
IPv6 can't be set to 8.8.8.8– user2551153
Jan 4 '16 at 16:23
Hi, Jeremy. Thanks for your input. I did try setting DNS to 8.8.8.8. When IPv4 DNS is set to 8.8.8.8 and IPv6 is set to auto, it works like this:
nslookup google.com Server: google-public-dns.a.google.com Address: 8.8.8.8 Non authoritative answer: Name: google.com Addresses: 2a00:1450:401 :801:200e 216.58.209.46
which I suppose is okay. When I set IPv4 to 8.8.8.8 and similarly IPv6 to 2001:4860:4860::8888 (IPv6 of google DNS) it works like this nslookup google.com Server: UnKnown Address: 2001:.... *** UnKnown can't find google.com: No response from server.
IPv6 can't be set to 8.8.8.8– user2551153
Jan 4 '16 at 16:23
2/2 ... And when I set IPv4 to 8.8.8.8 and disable IPv6 altogether, it works the same as when IPv6 is set to auto.
ping google.com
doesn't work in any of these cases.– user2551153
Jan 4 '16 at 16:24
2/2 ... And when I set IPv4 to 8.8.8.8 and disable IPv6 altogether, it works the same as when IPv6 is set to auto.
ping google.com
doesn't work in any of these cases.– user2551153
Jan 4 '16 at 16:24
add a comment |
The fact that the computer was recently reformatted could indicate a problem with the drivers for your network adapter(s).
Open "View network connections" and try disabling each adapter one-by-one. After disabling each one, test the DNS and then re-enable it. Perhaps you'll find one that's causing your DNS problems - if you do, you could try reinstalling the driver for that particular adapter.
It has to be a DNS problem. If you can ping the IP but it doesn't resolve, that's got to be the issue.
– user1780242
Dec 30 '15 at 2:35
Agreed, but DNS goes through the network adapter. It's entirely possible that the driver for the network adapter has a bug that's interfering with DNS. I was particularly suspicious of the "Microsoft Wi-Fi Direct Virtual Adapter" in your ipconfig dump. It's Microsoft-made, but I'm not clear on what it actually does.
– LevenTech
Dec 30 '15 at 4:16
Hi, man. OP here. I tried doing as you said, but all entries I see under 'view network connections' are: Ethernet (Realtek PCIe GBE Family Controller) and Wi-Fi (Network card Broadcom 802.11n). There was no Microsoft Wi-Fi Direct Virtual Adapter or anything else. I disabled / re-enabled both of them : the first one didn't really change a thing, and the second one was wi-fi so there was no connection whatsoever. I also tried following steps on windows.microsoft.com/en-us/windows/… but it produced same results.
– user2551153
Jan 4 '16 at 16:32
add a comment |
The fact that the computer was recently reformatted could indicate a problem with the drivers for your network adapter(s).
Open "View network connections" and try disabling each adapter one-by-one. After disabling each one, test the DNS and then re-enable it. Perhaps you'll find one that's causing your DNS problems - if you do, you could try reinstalling the driver for that particular adapter.
It has to be a DNS problem. If you can ping the IP but it doesn't resolve, that's got to be the issue.
– user1780242
Dec 30 '15 at 2:35
Agreed, but DNS goes through the network adapter. It's entirely possible that the driver for the network adapter has a bug that's interfering with DNS. I was particularly suspicious of the "Microsoft Wi-Fi Direct Virtual Adapter" in your ipconfig dump. It's Microsoft-made, but I'm not clear on what it actually does.
– LevenTech
Dec 30 '15 at 4:16
Hi, man. OP here. I tried doing as you said, but all entries I see under 'view network connections' are: Ethernet (Realtek PCIe GBE Family Controller) and Wi-Fi (Network card Broadcom 802.11n). There was no Microsoft Wi-Fi Direct Virtual Adapter or anything else. I disabled / re-enabled both of them : the first one didn't really change a thing, and the second one was wi-fi so there was no connection whatsoever. I also tried following steps on windows.microsoft.com/en-us/windows/… but it produced same results.
– user2551153
Jan 4 '16 at 16:32
add a comment |
The fact that the computer was recently reformatted could indicate a problem with the drivers for your network adapter(s).
Open "View network connections" and try disabling each adapter one-by-one. After disabling each one, test the DNS and then re-enable it. Perhaps you'll find one that's causing your DNS problems - if you do, you could try reinstalling the driver for that particular adapter.
The fact that the computer was recently reformatted could indicate a problem with the drivers for your network adapter(s).
Open "View network connections" and try disabling each adapter one-by-one. After disabling each one, test the DNS and then re-enable it. Perhaps you'll find one that's causing your DNS problems - if you do, you could try reinstalling the driver for that particular adapter.
answered Dec 30 '15 at 2:00
LevenTech
862415
862415
It has to be a DNS problem. If you can ping the IP but it doesn't resolve, that's got to be the issue.
– user1780242
Dec 30 '15 at 2:35
Agreed, but DNS goes through the network adapter. It's entirely possible that the driver for the network adapter has a bug that's interfering with DNS. I was particularly suspicious of the "Microsoft Wi-Fi Direct Virtual Adapter" in your ipconfig dump. It's Microsoft-made, but I'm not clear on what it actually does.
– LevenTech
Dec 30 '15 at 4:16
Hi, man. OP here. I tried doing as you said, but all entries I see under 'view network connections' are: Ethernet (Realtek PCIe GBE Family Controller) and Wi-Fi (Network card Broadcom 802.11n). There was no Microsoft Wi-Fi Direct Virtual Adapter or anything else. I disabled / re-enabled both of them : the first one didn't really change a thing, and the second one was wi-fi so there was no connection whatsoever. I also tried following steps on windows.microsoft.com/en-us/windows/… but it produced same results.
– user2551153
Jan 4 '16 at 16:32
add a comment |
It has to be a DNS problem. If you can ping the IP but it doesn't resolve, that's got to be the issue.
– user1780242
Dec 30 '15 at 2:35
Agreed, but DNS goes through the network adapter. It's entirely possible that the driver for the network adapter has a bug that's interfering with DNS. I was particularly suspicious of the "Microsoft Wi-Fi Direct Virtual Adapter" in your ipconfig dump. It's Microsoft-made, but I'm not clear on what it actually does.
– LevenTech
Dec 30 '15 at 4:16
Hi, man. OP here. I tried doing as you said, but all entries I see under 'view network connections' are: Ethernet (Realtek PCIe GBE Family Controller) and Wi-Fi (Network card Broadcom 802.11n). There was no Microsoft Wi-Fi Direct Virtual Adapter or anything else. I disabled / re-enabled both of them : the first one didn't really change a thing, and the second one was wi-fi so there was no connection whatsoever. I also tried following steps on windows.microsoft.com/en-us/windows/… but it produced same results.
– user2551153
Jan 4 '16 at 16:32
It has to be a DNS problem. If you can ping the IP but it doesn't resolve, that's got to be the issue.
– user1780242
Dec 30 '15 at 2:35
It has to be a DNS problem. If you can ping the IP but it doesn't resolve, that's got to be the issue.
– user1780242
Dec 30 '15 at 2:35
Agreed, but DNS goes through the network adapter. It's entirely possible that the driver for the network adapter has a bug that's interfering with DNS. I was particularly suspicious of the "Microsoft Wi-Fi Direct Virtual Adapter" in your ipconfig dump. It's Microsoft-made, but I'm not clear on what it actually does.
– LevenTech
Dec 30 '15 at 4:16
Agreed, but DNS goes through the network adapter. It's entirely possible that the driver for the network adapter has a bug that's interfering with DNS. I was particularly suspicious of the "Microsoft Wi-Fi Direct Virtual Adapter" in your ipconfig dump. It's Microsoft-made, but I'm not clear on what it actually does.
– LevenTech
Dec 30 '15 at 4:16
Hi, man. OP here. I tried doing as you said, but all entries I see under 'view network connections' are: Ethernet (Realtek PCIe GBE Family Controller) and Wi-Fi (Network card Broadcom 802.11n). There was no Microsoft Wi-Fi Direct Virtual Adapter or anything else. I disabled / re-enabled both of them : the first one didn't really change a thing, and the second one was wi-fi so there was no connection whatsoever. I also tried following steps on windows.microsoft.com/en-us/windows/… but it produced same results.
– user2551153
Jan 4 '16 at 16:32
Hi, man. OP here. I tried doing as you said, but all entries I see under 'view network connections' are: Ethernet (Realtek PCIe GBE Family Controller) and Wi-Fi (Network card Broadcom 802.11n). There was no Microsoft Wi-Fi Direct Virtual Adapter or anything else. I disabled / re-enabled both of them : the first one didn't really change a thing, and the second one was wi-fi so there was no connection whatsoever. I also tried following steps on windows.microsoft.com/en-us/windows/… but it produced same results.
– user2551153
Jan 4 '16 at 16:32
add a comment |
I just came across this same issue on a Windows 10 Dell tablet that one of my users brought into the office. Same issue, communications via IP work, but name resolution not working (aside from nslookup, oddly that was working fine).
After digging into this for a few minutes I also discovered that the tablet was missing a hostname entry when doing an ipconfig /all (same as shown in your screenshot above), so I went into the System properties and found that there was no computer name set in there. Added a computer name, rebooted, et voila! Name resolution is now working properly.
add a comment |
I just came across this same issue on a Windows 10 Dell tablet that one of my users brought into the office. Same issue, communications via IP work, but name resolution not working (aside from nslookup, oddly that was working fine).
After digging into this for a few minutes I also discovered that the tablet was missing a hostname entry when doing an ipconfig /all (same as shown in your screenshot above), so I went into the System properties and found that there was no computer name set in there. Added a computer name, rebooted, et voila! Name resolution is now working properly.
add a comment |
I just came across this same issue on a Windows 10 Dell tablet that one of my users brought into the office. Same issue, communications via IP work, but name resolution not working (aside from nslookup, oddly that was working fine).
After digging into this for a few minutes I also discovered that the tablet was missing a hostname entry when doing an ipconfig /all (same as shown in your screenshot above), so I went into the System properties and found that there was no computer name set in there. Added a computer name, rebooted, et voila! Name resolution is now working properly.
I just came across this same issue on a Windows 10 Dell tablet that one of my users brought into the office. Same issue, communications via IP work, but name resolution not working (aside from nslookup, oddly that was working fine).
After digging into this for a few minutes I also discovered that the tablet was missing a hostname entry when doing an ipconfig /all (same as shown in your screenshot above), so I went into the System properties and found that there was no computer name set in there. Added a computer name, rebooted, et voila! Name resolution is now working properly.
answered Sep 23 '16 at 16:31
MeNTaLMoNKeY
713
713
add a comment |
add a comment |
I had the same issue (probably after a heat crash). Took me hours to figure out that the HOSTNAME of the machine was deleted. Reentered it (including primary DNS-domain and workgroup name) and everything runs fine again. Good luck!
add a comment |
I had the same issue (probably after a heat crash). Took me hours to figure out that the HOSTNAME of the machine was deleted. Reentered it (including primary DNS-domain and workgroup name) and everything runs fine again. Good luck!
add a comment |
I had the same issue (probably after a heat crash). Took me hours to figure out that the HOSTNAME of the machine was deleted. Reentered it (including primary DNS-domain and workgroup name) and everything runs fine again. Good luck!
I had the same issue (probably after a heat crash). Took me hours to figure out that the HOSTNAME of the machine was deleted. Reentered it (including primary DNS-domain and workgroup name) and everything runs fine again. Good luck!
answered Dec 10 at 16:32
Martin
1
1
add a comment |
add a comment |
All the things suggested by other posters failed, so I resorted to drastic measures and did a full format with a fresh Win 10 install. It did work.
8
That's like "healing the disease by killing the patient". This shouldn't be the accepted answer.
– Fábio Antunes
Nov 27 '16 at 14:38
I agree. It's just that none of the suggestions worked and I did check each of them diligently. I'm sorry we couldn't reach a fruitful conclusion.
– user2551153
Mar 22 '17 at 13:49
add a comment |
All the things suggested by other posters failed, so I resorted to drastic measures and did a full format with a fresh Win 10 install. It did work.
8
That's like "healing the disease by killing the patient". This shouldn't be the accepted answer.
– Fábio Antunes
Nov 27 '16 at 14:38
I agree. It's just that none of the suggestions worked and I did check each of them diligently. I'm sorry we couldn't reach a fruitful conclusion.
– user2551153
Mar 22 '17 at 13:49
add a comment |
All the things suggested by other posters failed, so I resorted to drastic measures and did a full format with a fresh Win 10 install. It did work.
All the things suggested by other posters failed, so I resorted to drastic measures and did a full format with a fresh Win 10 install. It did work.
answered Jan 10 '16 at 17:43
user2551153
46116
46116
8
That's like "healing the disease by killing the patient". This shouldn't be the accepted answer.
– Fábio Antunes
Nov 27 '16 at 14:38
I agree. It's just that none of the suggestions worked and I did check each of them diligently. I'm sorry we couldn't reach a fruitful conclusion.
– user2551153
Mar 22 '17 at 13:49
add a comment |
8
That's like "healing the disease by killing the patient". This shouldn't be the accepted answer.
– Fábio Antunes
Nov 27 '16 at 14:38
I agree. It's just that none of the suggestions worked and I did check each of them diligently. I'm sorry we couldn't reach a fruitful conclusion.
– user2551153
Mar 22 '17 at 13:49
8
8
That's like "healing the disease by killing the patient". This shouldn't be the accepted answer.
– Fábio Antunes
Nov 27 '16 at 14:38
That's like "healing the disease by killing the patient". This shouldn't be the accepted answer.
– Fábio Antunes
Nov 27 '16 at 14:38
I agree. It's just that none of the suggestions worked and I did check each of them diligently. I'm sorry we couldn't reach a fruitful conclusion.
– user2551153
Mar 22 '17 at 13:49
I agree. It's just that none of the suggestions worked and I did check each of them diligently. I'm sorry we couldn't reach a fruitful conclusion.
– user2551153
Mar 22 '17 at 13:49
add a comment |
The answer is in the first section of the ipconfig
.
Windows IP Configuration
Host Name . . . . . . . . . . . . :
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Host name is blank.
Set the computer name in Control PanelSystem and SecuritySystem, and all will be well.
New contributor
add a comment |
The answer is in the first section of the ipconfig
.
Windows IP Configuration
Host Name . . . . . . . . . . . . :
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Host name is blank.
Set the computer name in Control PanelSystem and SecuritySystem, and all will be well.
New contributor
add a comment |
The answer is in the first section of the ipconfig
.
Windows IP Configuration
Host Name . . . . . . . . . . . . :
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Host name is blank.
Set the computer name in Control PanelSystem and SecuritySystem, and all will be well.
New contributor
The answer is in the first section of the ipconfig
.
Windows IP Configuration
Host Name . . . . . . . . . . . . :
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
Host name is blank.
Set the computer name in Control PanelSystem and SecuritySystem, and all will be well.
New contributor
edited Dec 25 at 6:16
Mureinik
2,33751525
2,33751525
New contributor
answered Dec 25 at 5:33
Mike Shurkin
1
1
New contributor
New contributor
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1019467%2fwindows-10-cant-resolve-hostnames-ping-with-ip-works-but-not-with-hostname%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
Is static IP and DNS working? From where are you getting DHCP info? Can you check you DHCP server configuration?
– g2mk
Dec 29 '15 at 21:31
If 192.168.0.1 is your router then try to remove 192.168.0.1 from its DNS servers... I guess that 217.172.224.160 is valid DNS server and just rejects external requests. Have you tried setup OpenDNS on your DHCP server?
– g2mk
Dec 29 '15 at 21:57
Hi, g2mk. OP here. I tried to follow your line of thought with some google-fu. Static IP and DNS do not work, I can tell that for sure. As for DHCP, I'm not sure how to reply to these questions. It is a standard and public-available DSL service supplied by one of the local Internet providers. Is DHCP on my side of things, or is it theirs? I tried following blogs.catapultsystems.com/jcwarner/archive/2011/06/27/… to get some info on my DHCP, but it doesn't recognize
show server
command. I'm not sure how to proceed.– user2551153
Jan 4 '16 at 17:01