Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with DNS names on different levels #91

Open
wclr opened this issue Jan 5, 2017 · 6 comments
Open

Issue with DNS names on different levels #91

wclr opened this issue Jan 5, 2017 · 6 comments

Comments

@wclr
Copy link

wclr commented Jan 5, 2017

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
Copy link
Owner

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

@wclr
Copy link
Author

wclr commented Jan 14, 2017

Ok, hope when you fix it you publish new built version on docker hub with #85 fix as well

@smazurov
Copy link

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
Copy link
Author

wclr commented Mar 2, 2017

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

@dsalahutdinov
Copy link

Hi, guys!
Could you please have a look at this #100
It is approach to solve this annoying issue 😄

@timotheemoulin
Copy link

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants