aacebedo / dnsdock

DNS service discovery for Docker containers
MIT License
606 stars 91 forks source link

Issue with DNS names on different levels #91

Open wclr opened 7 years ago

wclr commented 7 years ago

docker-compose.yaml contains two services with such definitions (stuff omitted)

service-client:
  labels:
    com.dnsdock.alias: "client.service.app.dev"

service:
  labels:  
    com.dnsdock.alias: service.app.dev

service-client container got IP 172.19.0.5 service container got IP 172.19.0.3

both address return two IP's:

> nslookup service.app.dev 127.0.0.1
Servidor:  localhost
Address:  127.0.0.1

Respuesta no autoritativa:
Nombre:  service.app.dev
Addresses:  172.19.0.5
          172.19.0.3

> nslookup client.serivce.app.dev 127.0.0.1
Servidor:  localhost
Address:  127.0.0.1

Respuesta no autoritativa:
Nombre:  client.service.app.dev
Addresses:  172.19.0.5
          172.19.0.3
aacebedo commented 7 years ago

I am working on this issue. This is a little bit more difficult than what I was expected to.

wclr commented 7 years ago

Ok, hope when you fix it you publish new built version on docker hub with https://github.com/aacebedo/dnsdock/issues/85 fix as well

smazurov commented 7 years ago

I also ran into this - for now my workaround is to not use tiered aliases for different services. Looking forward to the fix, let me know if I can help in some way.

wclr commented 7 years ago

hey, are you going to finish this? would be grateful for this.

dsalahutdinov commented 7 years ago

Hi, guys! Could you please have a look at this https://github.com/aacebedo/dnsdock/pull/100 It is approach to solve this annoying issue 😄

timotheemoulin commented 7 years ago

Hi @aacebedo do you have any input on this issue?