bash$ nslookup www.osdn.com -silent Server: 188.8.131.52 Address: 184.108.40.206#53 Non-authoritative answer: www.osdn.com canonical name = osdn.com. Name: osdn.com Address: 220.127.116.11
With nslookup you get back the DNS server you used and the port that server was at. You then find out that www.osdn.com is just an alias to the real name of osdn.com. The name osdn.com points to the IP address 18.104.22.168. So you found the IP address. Now let's try dig.
bash$ dig www.osdn.com ; <<>> DiG 9.1.0 <<>> www.osdn.com ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12056 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 2 ;; QUESTION SECTION: ;www.osdn.com. IN A ;; ANSWER SECTION: www.osdn.com. 17709 IN CNAME osdn.com. osdn.com. 17709 IN A 22.214.171.124 ;; AUTHORITY SECTION: osdn.com. 17709 IN NS ns2.andover.net. osdn.com. 17709 IN NS ns1.andover.net. ;; ADDITIONAL SECTION: ns1.andover.net. 104109 IN A 126.96.36.199 ns2.andover.net. 104109 IN A 188.8.131.52 ;; Query time: 24 msec ;; SERVER: 184.108.40.206#53(220.127.116.11) ;; WHEN: Tue Feb 26 10:30:50 2002 ;; MSG SIZE rcvd: 139
The dig command gives back more information than most people can easily understand. One way to start is to skip all of the lines that start with a semicolon. The semicolon lines are not very important. The data that comes back looks much like the format of a DNS configuration file. The first uncommented line is the one that says that www.osdn.com is an alias to osdn.com. The next line says that osdn.com points to 18.104.22.168. The next four uncommented lines tell you which DNS to talk to to get current correct information.