Nslookup and ping

WTF is happening there? Why first ping failed, but ping right after nslookup succeeded?

$ ping en.wikipedia.org
ping: cannot resolve en.wikipedia.org: Unknown host
$ nslookup en.wikipedia.org
Server:        192.168.0.1
Address:    192.168.0.1#53

Non-authoritative answer:
en.wikipedia.org    canonical name = wikipedia-lb.wikimedia.org.
wikipedia-lb.wikimedia.org    canonical name = wikipedia-lb.esams.wikimedia.org.
Name:    wikipedia-lb.esams.wikimedia.org
Address: 91.198.174.225

$ ping en.wikipedia.org
PING wikipedia-lb.esams.wikimedia.org (91.198.174.225): 56 data bytes
64 bytes from 91.198.174.225: icmp_seq=0 ttl=56 time=73.034 ms
64 bytes from 91.198.174.225: icmp_seq=1 ttl=56 time=75.222 ms
^C
--- wikipedia-lb.esams.wikimedia.org ping statistics ---
2 packets transmitted, 2 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 73.034/74.128/75.222/1.094 ms

>>1
Are you an idiot? en.wikipedia.org is in multiple servers. The moment you did nslookup en.wikipedia.org, your OS got DNS records, and an IP address to follow. After the DNS, your ping knows where to look. This happens on every OS, especially when your TTL had expired, or your DNS flushed.