Windows 7 cannot resolve ip hostname

Super User is a question and answer site for computer enthusiasts and power users. It only takes a minute to sign up. Connect and share knowledge within a single location that is structured and easy to search. The first paragraph looks a bit blank, perhaps something there? It doesn't resolve local hostnames either. The machine doesn't respond to pings from local network.

You can try to manually set the dns servers to the google ones: 8. 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. Added a computer name, rebooted, et voila! Name resolution is now working properly.

I had the same problem, but the hostname was present. Changing the hostname by adding a 2 to the end and then rebooting seems to have fixed the problem.

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. In my case, I have hyper-v manager installed and has one virtual switch that bridges my NIC with it.

This one works for me. Maybe Windows 10 or hyper-v has a buggy virtual switch. 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.

In my case setting the host name was not enough - it didn't help. I have no idea how did it happen to my PC, maybe after some system crash or during the recovery the entry went missing. Because there were some problems and I did recover my system with dism and sfc. So after I created this registry entry just with the empty value - it started working immediately even without reboot. It took me many hours and I tried probably everything I could google out until I finally bumped on the answer here - Windows 7 DNS not working nslookup IS working; ping -4 name.

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. Sign up to join this community. The best answers are voted up and rise to the top. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams?

Learn more. Windows 10 can't resolve hostnames - ping with IP works but not with hostname Ask Question. Asked 6 years ago. When you enter Bing. There are seven methods of resolving names. Three are used primarily, with hostnames used on the Internet and internal networks.

Broadcasts are usually used as a last resort to help minimize broadcast traffic on a network. The client broadcasts the name onto the network, and if the host with that name is on the network, it will respond with the IP address. Remember though, broadcasts do not cross routers, so the broadcast name resolution method is good only for the same subnet.

Name resolution methods are tied to two types of names:. A host name can be up to characters in length and is the only type of name used on the Internet. When a hostname is combined with a domain name, it becomes a fully qualified domain name FQDN. For example, a Windows 7 PC named Client1 in the domain wiley. Hostnames are primarily resolved by DNS servers.

The use of NetBIOS names has been significantly reduced in networks in favor of hostnames, but they are still being used by older applications. While DNS is the primary method used to resolve hostnames, it's not the only method.

There are three primary methods used to resolve hostnames:. DNS servers answer queries for name resolution of hostnames. This forwarding occurs on internal networks and on the Internet. Hosts file. Entries in the Hosts file are automatically placed into the host cache. Malware sometimes modifies the Hosts file to prevent a client from accessing specific websites.

For example, a bogus entry could be placed in the file for Microsoft's update site, and the client would no longer be able to get updates. Host cache. Once a name is resolved by DNS, the result is placed in the host cache also called the DNS cache, which is a little misleading because this cache also holds entries from the Hosts file. This will remove all entries that were cached from a DNS query, but it will not remove entries placed in cache from the Hosts file.

Enter the following command to resolve a name using DNS:. The first line should be something like this:. Resolving hostnames and IP addresses over a VPN is different from resolving hostnames over a local network with a domain, and still a bit different than just having a workgroup setup with a few computers that doesn't have a domain, AD, internal DNS server, hardware firewall or UTM implementation. Start from the beginning, walk us through what you are trying to do, and tell us your network layout and hardware configuration.

I have a bunch of servers with private IP addresses that need to communicate with each other using their hostname. They do not belong to a domain. Installed on my network is a DNS server that handles both internal and external requests I've heard this is risky.

Looking to change it soon. So, even though I have the hostname. To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Hello guys, How can I get my windows machine's hostname to resolve to its IP? Any help? Microsoft Corporation Windows Server R2 Best Answer.

Krizz This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. That's the key information. Problem is, that on domain machines any attempt to communicate with non-domain hostname will fallback to suffixing domain name to hostname. So each time you ping hostname1 whether it's domain or non-domain machine , you will be pinging hostname1.