Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNS Listen IP #19

Open
whitefi opened this issue May 1, 2020 · 4 comments
Open

DNS Listen IP #19

whitefi opened this issue May 1, 2020 · 4 comments

Comments

@whitefi
Copy link

whitefi commented May 1, 2020

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

@whitefi
Copy link
Author

whitefi commented May 1, 2020

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

But could be a FR.

@schniggie
Copy link

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.

@theguly
Copy link

theguly commented May 14, 2020

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?

@whitefi
Copy link
Author

whitefi commented May 14, 2020

Is not mandatory, but useful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants