Le mardi 17 août 2010, Tanguy Ortolo a écrit : > To know the result of that resolution, a software such as host(1) is not > appropriate, as it would only do DNS resolution. So, as I found no > software implementing a command-line interface to query the system > resolver, I coded the attached tool. I called it resolv, that may or may > not be a good name.
Sorry, I forgot to give some examples. DNS, IPv4: $ resolv www.gnu.org Name: gnu.org Aliases: www.gnu.org Address type: inet Address length: 4 Addresses: 199.232.41.10 DNS, IPv4 and IPv6: $ resolv www.kame.net Name: orange.kame.net Aliases: www.kame.net Address type: inet Address length: 4 Addresses: 203.178.141.194 Name: orange.kame.net Aliases: www.kame.net Address type: inet6 Address length: 16 Addresses: 2001:200:dff:fff1:216:3eff:feb1:44d7 mDNS, IPv4 and IPv6: $ resolv tolkien.local Name: tolkien.local Aliases: Address type: inet Address length: 4 Addresses: 10.100.14.191 Name: tolkien.local Aliases: Address type: inet6 Address length: 16 Addresses: fe80::21c:23ff:fe3f:ffbb Static file, IPv4 and IPv6: $ resolv localhost Name: localhost Aliases: ip4-localhost ip6-localhost ip6-loopback Address type: inet Address length: 4 Addresses: 127.0.0.1 127.0.0.1 Name: localhost Aliases: ip6-localhost ip6-loopback Address type: inet6 Address length: 16 Addresses: ::1 -- Tanguy Ortolo
signature.asc
Description: Digital signature
