Re: DNS suffix for resolver

2017-07-13 Thread Aleksandar Lazic 
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 <al-hapr...@none.at> 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

Re: DNS suffix for resolver

2017-07-13 Thread Baptiste 
On Wed, Jul 12, 2017 at 11:41 PM, Aleksandar Lazic 
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

DNS suffix for resolver

2017-07-12 Thread Aleksandar Lazic 
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?

###
oc rsh haproxy17-3-gd94c haproxy -vv
HA-Proxy version 1.7.8 2017/07/07
Copyright 2000-2017 Willy Tarreau 

Build options :
  TARGET  = linux2628
  CPU = generic
  CC  = gcc
  CFLAGS  = -O2 -g -fno-strict-aliasing -Wdeclaration-after-statement -fwrapv
  OPTIONS = USE_LINUX_SPLICE=1 USE_GETADDRINFO=1 USE_ZLIB=1 USE_REGPARM=1 
USE_OPENSSL=1 USE_LUA=1 USE_PCRE=1 USE_PCRE_JIT=1 USE_TFO=1

Default settings :
  maxconn = 2000, bufsize = 16384, maxrewrite = 1024, maxpollevents = 200

Encrypted password support via crypt(3): yes
Built with zlib version : 1.2.7
Running on zlib version : 1.2.7
Compression algorithms supported : identity("identity"), deflate("deflate"), 
raw-deflate("deflate"), gzip("gzip")
Built with OpenSSL version : OpenSSL 1.0.1e-fips 11 Feb 2013
Running on OpenSSL version : OpenSSL 1.0.1e-fips 11 Feb 2013
OpenSSL library supports TLS extensions : yes
OpenSSL library supports SNI : yes
OpenSSL library supports prefer-server-ciphers : yes
Built with PCRE version : 8.32 2012-11-30
Running on PCRE version : 8.32 2012-11-30
PCRE library supports JIT : yes
Built with Lua version : Lua 5.3.4
Built with transparent proxy support using: IP_TRANSPARENT IPV6_TRANSPARENT 
IP_FREEBIND

Available polling systems :
  epoll : pref=300,  test result OK
   poll : pref=200,  test result OK
 select : pref=150,  test result OK
Total: 3 (3 usable), will use epoll.

Available filters :
[COMP] compression
[TRACE] trace
[SPOE] spoe
###

-- 
Best Regards
Aleks