kgretzky / pwndrop

Self-deployable file hosting service for red teamers, allowing to easily upload and share payloads over HTTP and WebDAV.

Home Page:https://breakdev.org/pwndrop

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

DNS Listen IP

whitefi opened this issue · comments

When deployed with a private IP address and using a public IP to NAT it is not possible to use the nameserver feature.

Is is possible to have the listen IP set to the private IP so it can bind to the ports but have an option for DNS response IP set to the public NAT IP.

Currently when using the private IP as the listen IP and using NAT, the DNS server replies with the private listen IP in the DNS response

NVM, I'll stop being lazy and build from source and change the DNS IP in server.go.

But could be a FR.

I also needed this feature and did a fork. I added response_ip as config parameter, there you can set the IP address that is used by all DNS responses. And listen_ip is only the IP, where pwndrop will be bond to. You can find it here. There is no binary release, you have to built it yourself. Btw. I also included a docker setup based on docker-pwndrop.

commented

wondering if DNS is a mandatory service or just a feature. do you think it could be possible to enable/disable it while working on bind-ip config option?

Is not mandatory, but useful.