Search results
Results from the WOW.Com Content Network
In case there's no reverse ptr for ping -a <ip> or nslookup <ip> to show, you can run ipconfig /displaydns | clip, open a text editor, paste, and search for the IP there. Note that this will work only if the original DNS query was done via the Windows DNS resolver - some apps do their own DNS queries, like newer browsers using DNS-over-HTTPS .
There are some IP address that nslookup can't resolve (both on Windows and Linux). Problem: I can find the IP of the hostname, but reverse lookup fails. PS C:\\> nslookup.exe somehost2 Server: c...
Command 8) nslookup 174.3.217.172.in-addr.arpa - You may be wondering if you can use the traditional reverse DNS lookup method with nslookup as we did in Command 1 with dig. You can. Notice the same nslookup failings as I listed above (Command 6) between this command and the one with the -type=PTR flag set below (Command 9):
When you run nslookup, the DNS client tries to find the name of the DNS server that it's configured to use by sending a PTR query to that DNS server. If there's no reverse lookup zone (and therefore no PTR records) it gives the message that the server is uknown. Reverse lookup zones are not required, so not having one won't do any harm.
The comments that the tools are all the same is wrong. Host/dig work essentially the same way, but nslookup does several undesirable things. The following page provides a good explanation of the flaws with nslookup.
Nslookup will try to resolve the name for the ip address of the DNS server configured as the primary DNS server on the client by performing a reverse lookup of the ip address. If you don't have a rDNS zone set up for your network/subnet you'll get the "server unknown" message as nslookup will be unable to resolve the name for the ip address.
If you're using nslookup it's this (assuming 192.168.0.1 as the IP in question) > set type=ptr > 1.0.168.192.in-addr.arpa EDIT: Remember a reverse lookup only works if there is a PTR record created for the IP, and it's not guaranteed to return the hostname you're looking for. Completely depends on how DNS is configured and maintained in your ...
Stack Exchange Network. Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
Basically, it's what the name says it is. An authoritative answer comes from a nameserver that is considered authoritative for the domain which it's returning a record for (one of the nameservers in the list for the domain you did a lookup on), and a non-authoritative answer comes from anywhere else (a nameserver not in the list for the domain you did a lookup on).
I thought I could fix this by using my hosts file to avoid the need for a lookup. I added an entry to my hosts file like this. 127.0.0.1 myMachine.MyDnsSuffix But this didn't change the load times, even after a reboot. Although it is not important to resolve this specific problem, I would really like to know why this happens.