Am 05.04.2014 18:06, schrieb /dev/rob0: > One other comment to this thread: please, PLEASE, get rid of > nslookup. It is broken, bug-ridden garbage that will not be fixed. > Nobody in A.D. 2014 should be recommending it. The proper tool for > DNS troubleshooting is dig(1)
agreed, but until now i found no way to do the PTR request with dig or was not interested that much to dig docs instead just type or find it absurd that "dig PTR 8.8.8.8" don't work [harry@srv-rhsoft:~]$ nslookup 8.8.8.8 Server: 127.0.0.1 Address: 127.0.0.1#53 Non-authoritative answer: 8.8.8.8.in-addr.arpa name = google-public-dns-a.google.com. Authoritative answers can be found from: 8.8.8.in-addr.arpa nameserver = ns3.google.com. 8.8.8.in-addr.arpa nameserver = ns4.google.com. 8.8.8.in-addr.arpa nameserver = ns2.google.com. 8.8.8.in-addr.arpa nameserver = ns1.google.com. ns1.google.com internet address = 216.239.32.10 ns4.google.com internet address = 216.239.38.10 ns3.google.com internet address = 216.239.36.10 ns2.google.com internet address = 216.239.34.10
