On 2019-10-23 11:40, Mike Easter wrote:
Lu Wei wrote:
I accidentally found that "nslookup" works even if I specify a
non-existent dns server. For example "lookup www.kingoffighters.com
202.30.50.1" will return nothing for the first time but return correct
result for the second. 202.30.50.1 is just a random typed address.Â* Is
this normal?

My linux nslookup uses the default sequence of nameservers if the
command designated one doesn't work/ fails.Â* If the first default fails
then it uses the next, etc.

Likely Win has a similar strategy.

I think that possibility should be excluded because I see in Wireshark
log that exact "ghost" server returned the dns answer.
The snapshot:
http://androidhost.org/v27jSOB
--
Regards,
Lu Wei
IM:
PGP: 0xA12FEF7592CCE1EA