Does dns-proxy-server support network-scoped aliases for a container?

[groall]

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)

[mageddo]

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]

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]

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