[GH-ISSUE #86] add container name #39

Closed
opened 2026-02-26 04:33:51 +03:00 by kerem · 6 comments
Owner

Originally created by @antarus on GitHub (Aug 17, 2018).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/86

Hello, would it be possible to add the management of container names a bit like https://github.com/dvddarias/docker-hoster.

If I launch services via docker-compose, I would like to be able to access them with their name without having to add a configuration hostname.

thanks

Originally created by @antarus on GitHub (Aug 17, 2018). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/86 Hello, would it be possible to add the management of container names a bit like https://github.com/dvddarias/docker-hoster. If I launch services via docker-compose, I would like to be able to access them with their name without having to add a configuration hostname. thanks
kerem 2026-02-26 04:33:51 +03:00
  • closed this issue
  • added the
    feature
    label
Author
Owner

@mageddo commented on GitHub (Aug 19, 2018):

I think it makes sense. You mean solve by container name or docker-compose service name?

<!-- gh-comment-id:414097350 --> @mageddo commented on GitHub (Aug 19, 2018): I think it makes sense. You mean solve by container name or docker-compose service name?
Author
Owner

@antarus commented on GitHub (Aug 20, 2018):

container name and docker-compose service name seem good :D

<!-- gh-comment-id:414216203 --> @antarus commented on GitHub (Aug 20, 2018): container name and docker-compose service name seem good :D
Author
Owner

@mageddo commented on GitHub (Oct 5, 2018):

Hello @antarus

Feature was developed and it's on this branch. The way to use it's documented here.

Points

  • .docker suffix was used by convention as every FQDN must have an domain
  • Feature is disabled by default cause all previous versions haven't it, so will keep it disabled to make DPS in a standard behavior
  • Feature can be activated by command line, json conf or environment variable as documented at the docs

Please tell me if you agree with the feature?

<!-- gh-comment-id:427228070 --> @mageddo commented on GitHub (Oct 5, 2018): Hello @antarus Feature was developed and it's [on this branch](https://github.com/mageddo/dns-proxy-server/blob/feature/86). The way to use it's [documented here](https://github.com/mageddo/dns-proxy-server/blob/feature/86/docs/features.md#access-container-by-its-container-name--service-name). **Points** * `.docker` suffix was used by convention as every FQDN [must have an domain](https://en.wikipedia.org/wiki/Domain_name) * Feature is disabled by default cause all previous versions haven't it, so will keep it disabled to make DPS in a standard behavior * Feature can be activated by command line, json conf or environment variable as documented at the docs Please tell me if you agree with the feature?
Author
Owner

@mageddo commented on GitHub (Oct 5, 2018):

Checkout the pull request #88

<!-- gh-comment-id:427228205 --> @mageddo commented on GitHub (Oct 5, 2018): Checkout the pull request #88
Author
Owner

@mageddo commented on GitHub (Oct 6, 2018):

New version was released https://github.com/mageddo/dns-proxy-server/releases/tag/2.7.0

<!-- gh-comment-id:427601240 --> @mageddo commented on GitHub (Oct 6, 2018): New version was released https://github.com/mageddo/dns-proxy-server/releases/tag/2.7.0
Author
Owner

@antarus commented on GitHub (Oct 8, 2018):

perfect thanks

<!-- gh-comment-id:427828135 --> @antarus commented on GitHub (Oct 8, 2018): perfect thanks
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/dns-proxy-server-mageddo#39
No description provided.