mirror of
https://github.com/mageddo/dns-proxy-server.git
synced 2026-04-25 17:35:54 +03:00
[GH-ISSUE #192] Change the IP address that the dns-proxy-server operates on. #76
Labels
No labels
bug
confirmed
discussion
duplicate
enhancement
feature
feature-request
not-planned
pull-request
secondary-feature
stale
triage
waiting-feedback
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/dns-proxy-server-mageddo#76
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @trapeze-bell-peter on GitHub (Mar 25, 2020).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/192
I have posted this also as a question on Stackflow.
I am using mageddo/dns-proxy-server in my RoR environment to provide DNS resolution for the docker containers. This works like a treat until I connect to the company VPN. Unfortunately, dns-proxy-server binds to the port 172.17.0.2 which conflicts with the VPN. My other containers are using a different IP range.
I am wondering whether there is a way to get dns-proxy-server to bind to a different IP address to avoid the conflict with the VPN.
Many thanks in advance.
@mageddo commented on GitHub (Apr 28, 2020):
@trapeze-bell-peter you can specify DPS container IP on the start, see
@mageddo commented on GitHub (Jul 10, 2020):
Not sure if my answer helped, feel free to continue the discussion if need it
@trapeze-bell-peter commented on GitHub (Jul 10, 2020):
Really sorry. I thought I had answered. Your answer was perfect!