If this is your first visit, be sure to
check out the Forum Rules by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Honestly, I don't know by now.
I renamed the .msf3 directory in my home directory, then metasploit started up normal. Then I copied back the config file which resides in the .msf3 directory - and it is still working (which means no DNS lookup). Weird.
I'll make some other tests later since I want to know what was going on there.

Ok, so I performed some more tests.
After copying the config file back to the .msf3 directory msfconsole works fine, as far as I tested it till now (I tried a few exploits against my unpatched win2k box).

Doing the same procedure with msfweb or msfgui both tools are crashing each time at the point of selecting the target, since meetasploit again performs this ominous DNS lookup (checking with tcpdump).

When I remove the config file msfweb and msfgui work as expected. So there must be something in my config file which triggers this DNS lookup behaviour. But why is msfconsole working with that???
That's really weird.

Ok, so I performed some more tests.
After copying the config file back to the .msf3 directory msfconsole works fine, as far as I tested it till now (I tried a few exploits against my unpatched win2k box).

Doing the same procedure with msfweb or msfgui both tools are crashing each time at the point of selecting the target, since meetasploit again performs this ominous DNS lookup (checking with tcpdump).

When I remove the config file msfweb and msfgui work as expected. So there must be something in my config file which triggers this DNS lookup behaviour. But why is msfconsole working with that???
That's really weird.

Think you could post up your config file for us?

"The goal of every man should be to continue living even after he can no longer draw breath." ~ShadowKill