I am currently experiencing issues accessing one of my client’s servers, and it appears to be a problem with the network connection between my computer and the server. I attempted to troubleshoot by using the nslookup command in the Windows command line to retrieve the server’s IP address, but it did not work. Running any nslookup command returns “No response from server.” For example, when I run “nslookup www.google.com,” I get the following output:
C:\Windows\system32>nslookup www.google.com
Server: UnKnown
Address: 2606:4700:4700::1111
*** UnKnown can't find www.google.com: No response from server
I have set my DNS to use Cloudflare, but the same issue occurs when using my provider’s DNS or Google’s DNS. I am able to access and use the internet without issue, indicating that my DNS is working. Can anyone suggest why nslookup may not be working for me? Here is the output of my “ipconfig /all” command:
C:\Windows\system32>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : Wildfire
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. . . . . . . . . : 9C-5A-44-3C-4D-9E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Local Area Connection* 1:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter
Physical Address. . . . . . . . . : 48-F1-7F-C2-ED-9B
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Local Area Connection* 10:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Wi-Fi Direct Virtual Adapter #2
Physical Address. . . . . . . . . : 4A-F1-7F-C2-ED-9A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Killer(R) Wireless-AC 1550i Wireless Network Adapter (9560NGW) 160MHz
Physical Address. . . . . . . . . : 48-F1-7F-C2-ED-9A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::30b6:eeab:4d53:b8e4%9(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.1.107(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Lease Obtained. . . . . . . . . . : 21. listopada 2019. 9:09:22
Lease Expires . . . . . . . . . . : 21. listopada 2019. 11:09:21
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DHCPv6 IAID . . . . . . . . . . . : 105443711
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-24-ED-51-AC-9C-5A-44-3C-4D-9E
DNS Servers . . . . . . . . . . . : 2606:4700:4700::1111
2606:4700:4700::1001
1.1.1.1
1.0.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
Ethernet adapter Bluetooth Network Connection:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Bluetooth Device (Personal Area Network)
Physical Address. . . . . . . . . : 48-F1-7F-C2-ED-9E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Ethernet adapter vEthernet (Default Switch):
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Hyper-V Virtual Ethernet Adapter
Physical Address. . . . . . . . . : 00-15-5D-F7-39-02
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::fd51:db6:50fd:5d6b%23(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.46.225(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . :
DHCPv6 IAID . . . . . . . . . . . : 385881437
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-24-ED-51-AC-9C-5A-44-3C-4D-9E
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
C:\Windows\system32>
3 Answers
Introduction
The nslookup command is a useful tool for retrieving the IP address of a server. However, sometimes it may not work due to various reasons, such as network connectivity issues or incorrect DNS settings. In this blog post, we will discuss how to get the IP address of a server when nslookup is not working.
Check Network Connectivity
Before troubleshooting the nslookup command, it is important to ensure that your computer is connected to the network. You can do this by checking your network settings and verifying that your computer has an active network connection. If you are using a wired connection, make sure that your Ethernet cable is properly plugged in. If you are using a wireless connection, make sure that your computer is connected to the correct network and that the signal strength is strong enough.
If you are still unable to connect to the network, try restarting your computer, modem, and router. This can help refresh your network settings and resolve any connectivity issues. If the problem persists, contact your network administrator or internet service provider (ISP) for further assistance.
Use Ping Command
If the nslookup command is not working, you can try using the ping command to retrieve the IP address of a server. The ping command sends packets of data to a server and measures the response time, which can help determine the server’s IP address.
To use the ping command, open the Windows command prompt and type “ping [server name]” (without the quotes). For example, if you want to retrieve the IP address of the Google server, you can type “ping www.google.com” in the command prompt. The output will display the IP address of the server, as well as the response time.
If the ping command is successful, you can use the retrieved IP address to access the server. However, if the ping command is unsuccessful, it may indicate that the server is down or not responding.
Check Firewall Settings
Another reason why nslookup may not be working is due to firewall settings. Firewalls are designed to protect your computer from unauthorized access and can sometimes block incoming or outgoing connections, including the nslookup command.
To check your firewall settings, open the Windows Security app and click on “Firewall & network protection.” From there, you can view your firewall settings and make any necessary changes. If you are unsure about which settings to change, contact your network administrator or ISP for assistance.
Use Tracert Command
If the ping command is not successful, you can try using the tracert command to trace the network path to the server. The tracert command sends packets of data to the server and displays the network path, as well as the response time for each hop.
To use the tracert command, open the Windows command prompt and type “tracert [server name]” (without the quotes). For example, if you want to trace the network path to the Google server, you can type “tracert www.google.com” in the command prompt.
The output will display the IP address of each hop, as well as the response time. This can help identify any network connectivity issues and determine the server’s IP address.
Manually Check DNS Settings
If none of the above methods work, you can manually check your DNS settings to ensure that they are correct. To do this, open the Windows command prompt and type “ipconfig /all” (without the quotes).
The output will display your network settings, including your DNS server addresses. Make sure that the DNS server addresses are correct and match your network settings. If they are incorrect, you can change them by accessing your network settings and updating the DNS server addresses.
Conclusion
In conclusion, the nslookup command is a useful tool for retrieving the IP address of a server. However, if it is not working, there are several other methods that you can use to retrieve the server’s IP address, such as the ping command, tracert command, and manually checking your DNS settings. By following these troubleshooting steps, you can ensure that your computer is connected to the network and access the server without any issues.
There are several possible reasons why nslookup is not working for you. One possible issue is that there is a problem with your DNS settings. You can try resetting your DNS settings to their default values by running the command “ipconfig /flushdns” in the command line. Additionally, you can try running the command “nslookup” with the IP address of the server instead of the hostname to see if that resolves the issue.
Another possible issue could be that there is a problem with your network connection. You should check if your computer is connected to the internet and check the status of your network adapter by running “ipconfig /all” command. Also, you could try to troubleshoot your network connection by disabling and re-enabling your network adapter, or resetting your router.
Lastly, the problem could be with the server itself. In this case, you should contact the server administrator to see if they are aware of any issues with the server or network.
It appears that you have IPv6 addresses for CloudFlare’s DNS servers configured, but you don’t have an IPv6 address assigned to your own device. Your internet access is limited to IPv4. Many programs will automatically switch to a different DNS server if the first one is unavailable, however nslookup does not have this feature and will continue to try the first server in the list.
To fix this issue, you can open the IPv6 configuration window, for example, using the ncpa.cpl command, and set the “DNS servers” option to “Automatic”.