[GH-ISSUE #234] Does dns-proxy-server support network-scoped aliases for a container? #92

New issue

Closed

opened 2026-02-26 04:34:01 +03:00 by kerem · 3 comments

kerem commented

2026-02-26 04:34:01 +03:00

Owner

Originally created by @groall on GitHub (Dec 3, 2021).
Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/234

What is expected

Doed dns-proxy-server support network-scoped aliases for the container?

What is Happening

I use aliases to connect containers to each other by a domain like in production. It works with a proxy server for http requests from a host or with coredns for other type request. But using coredns has the problem: from time to time a host OS doesnt use it due to rewriting resolf.conf. DPS overwrites resolv.conf and I would be like to use it instead of coredns to access containers by alias.

Changes (Optional)

Originally created by @groall on GitHub (Dec 3, 2021). Original GitHub issue: https://github.com/mageddo/dns-proxy-server/issues/234 ### What is expected Doed dns-proxy-server support network-scoped aliases for the container? ### What is Happening I use aliases to connect containers to each other by a domain like in production. It works with a proxy server for http requests from a host or with coredns for other type request. But using coredns has the problem: from time to time a host OS doesnt use it due to rewriting resolf.conf. DPS overwrites resolv.conf and I would be like to use it instead of coredns to access containers by alias. ### Changes (Optional)

kerem

2026-02-26 04:34:01 +03:00

closed this issue
added the
discussion

waiting-feedback
labels

kerem commented

2026-02-26 04:34:01 +03:00

Author

Owner

@mageddo commented on GitHub (Mar 2, 2023):

Hey,

By network scoped you mean this feature?

Containers on the default bridge network can only access each other by IP addresses, unless you use the --link option, which is considered legacy. On a user-defined bridge network, containers can resolve each other by name or alias.

I already used it without DPS but never tested it with DPS to be honest, I will take a look at that and see if it works somehow or how far we are to get it working.

For now, I think you can configure coredns address as a DPS remote server then it would solve the solve the container by alias, give it a try.

@mageddo commented on GitHub (Mar 2, 2023): Hey, By network scoped you mean [this feature][1]? > Containers on the default bridge network can only access each other by IP addresses, unless you use the [--link option](https://docs.docker.com/network/links/), which is considered legacy. On a user-defined bridge network, containers can resolve each other by name or alias. I already used it without DPS but never tested it with DPS to be honest, I will take a look at that and see if it works somehow or how far we are to get it working. For now, I think you can configure coredns address as a DPS remote server then it would solve the solve the container by alias, give it a try. [1]: https://docs.docker.com/network/bridge/#differences-between-user-defined-bridges-and-the-default-bridge

kerem commented

2026-02-26 04:34:01 +03:00

Author

Owner

@mageddo commented on GitHub (Mar 2, 2023):

But using coredns has the problem: from time to time a host OS doesnt use it due to rewriting resolf.conf.

If your Linux has systemd-resolved installed then this issue will be resolved, try DPS 3.5.2, see #321

@mageddo commented on GitHub (Mar 2, 2023): > But using coredns has the problem: from time to time a host OS doesnt use it due to rewriting resolf.conf. If your Linux has systemd-resolved installed then this issue will be resolved, try DPS 3.5.2, see #321

kerem commented

2026-02-26 04:34:01 +03:00

Author

Owner

@mageddo commented on GitHub (May 29, 2024):

Closing this issue, feel free to reopen it when you are able to respond

@mageddo commented on GitHub (May 29, 2024): Closing this issue, feel free to reopen it when you are able to respond

kerem referenced this issue

2026-02-26 04:34:40 +03:00

[PR #93] [MERGED] Feature/92 #264

kerem referenced this issue

2026-02-26 04:34:40 +03:00

[PR #95] [MERGED] Feature/92 #266