For complicated reasons, I have been forced to make an identical copy of cmd.exe
and rename it to cmd-2.exe
, which I put as a shortcut on the Taskbar to have them "grouped" in different taskbar groups.
Sometimes, I forget about this, and to open a new cmd.exe
I middle-click that Taskbar icon to open a new cmd.exe
. I then type a command such as dir
and it spits out a bunch of nonsense, including: DNS bad key
, which only happens if I accidentally use cmd-2.exe
, not if I open the "real" cmd.exe
, so it's not a "practical" problem.
However, I wonder why that message is ever printed at all. Is it apparently failing to do some kind of DNS lookup or something? Why is DNS involved at all with issuing dir
to list files on my local computer? I have no network set up, no cloud drives, nothing like that whatsoever. It scares me that (apparently) there are DNS queries being made when I issue dir
.
Maybe DNS bad key
refers to something completely unrelated to the Domain Name System? I don't know what a "bad key" would even be in that context.