Since you didn't post any output to your command I'll show the answer section of two subsequent queries:
www.wikipedia.org. 21297 IN CNAME dyna.wikimedia.org.
dyna.wikimedia.org. 57 IN A 91.198.174.192
ˆˆˆˆˆ
and
www.wikipedia.org. 21181 IN CNAME dyna.wikimedia.org.
dyna.wikimedia.org. 157 IN A 91.198.174.192
ˆˆˆˆˆ
Notice that they are NOT identical. 4 of the 5 fields appear static, but one is definitely changing.
An DNS answer section looks like:
<name> <TTL> <class> <type> <record data>
Finding the reason for the different TTL values is probably your homework assignment.
Hint:
Investigate what a TTL is supposed to mean for DNS records and caching them.
You should learn why my example with a second query showing a higher, rather than a lower TTL value in the second response from caching/recursive nameserver is a-typical.
What can you infer from the fact that a TTL value increases between subsequent queries?
Answer 3: With big public resolver like Google's
8.8.8.8 your subsequent queries won't be answered by a single server, but each query will most likely be answered by a different, random server from much larger cluster/pool.