Title: Re: DNS suffix for resolver
Hi Baptiste,
Baptiste wrote on 13.07.2017:
|
On Wed, Jul 12, 2017 at 11:41 PM, Aleksandar Lazic <[email protected]> wrote:
|
Hi,
I have used today again my haproxy image
https://hub.docker.com/r/me2digital/haproxy17/ in openshift.
There is a variable SERVICE_DEST which have the destination hostname for
the server line in haproxy.
When I use just mongodb, that's the service name in openshift, it will
not resolve because the resolver does not respect the 'search' line.
###
oc rsh haproxy17-3-gd94c cat /etc/resolv.conf
search 1-mongodb-test.svc.cluster.local svc.cluster.local cluster.local esrv.local
nameserver 10.40.96.55
nameserver 10.40.96.55
options ndots:5
###
will this be better handled with 1.8 dns code?
|
Hi Aleksandar,
There is nothing in 1.8 regarding the search option. For now DNS resolution only supports fqdn.
I'm seeing attraction for such type of feature and I saw myself a few use cases where it looks to be interesting to support it.
I can dig into it and see if this can be done in a simple yet efficient way. I can't promise anything for 1.8 release though...
Baptiste |
Thanks to take a look.
--
Best Regards
Aleks
