recon-ng icon indicating copy to clipboard operation
recon-ng copied to clipboard

Default NAMESERVER issues

Open hlein opened this issue 4 years ago • 1 comments

By default, recon-ng uses the hardcoded default 8.8.8.8 as its nameserver.

There's various reasons one might not want to use that - information leakage, being in a closed environment, having local firewall rules that only allow DNS out to expected nameservers, etc.

The default can be overridden, but only with a specific, static IP.

It would be nice if recon-ng used the system resolver default (typically from /etc/resolv.conf), and/or had a knob that one could turn, like options set NAMESERVER system.

Also, when a lookup does fail, the error is not very informative, just: [!] Invalid nameserver.

If that included the IP that recon-ng tried as a nameserver and couldn't talk to, that would make it more obvious what was wrong.

Opinions? Would recon-ng accept PR(s) that added system-nameserver as an option/default, and/or improved those errors?

hlein avatar Apr 27 '22 20:04 hlein

I think that's a great idea. It would need to be designed with cross-compatibility in mind though. Yes, I accept PRs.

lanmaster53 avatar May 02 '24 21:05 lanmaster53