Rex socks server doesn't do remote name resolution about metasploit-framework HOT 3 CLOSED

Are you trying to start a Rex::Socket::TcpServer on a remote host by hostname?

This won't play well because the only proper way to do that (aside from the IRB trick you taught me) is to add a route to the remote host's IP, once its in the switchboard rex can start sockets on it. Problem is that we dont have name resolution for hosts on the switchboard IIRC. Spoke with HDM about the remote servers as well, primarily to do a rev-portfwd but also to start things like http servers/session handlers on remote (which we can do now), and we would ideally have each host's available IP addrs enumerated on session start and added to the switchboard. Even if that were done, you'd still have the problem of a host with multiple IPs having a single hostname so starting the TcpServer would either require an iface or it would need to start on all iface's which resolve to that hostname locally. Calling a gethostbyname for the local machine name should give us all the IPs though... hmm.

from metasploit-framework.

#579 Should bring us closer to being able to resolve on the fly. Still need to have nameservers defined for routed subnets, but now we can use net-dns over Rex to do the resolution.

from metasploit-framework.

This kind of looks more like a mailing list discussion at this point, and less like a bug report or feature request. If it's not, please open a bug on Redmine?

from metasploit-framework.