DNS discovering service with same name in another stack

[markwylde]

I'm not sure if this is a bug or by design, but it's not having the result I would expect.

• I create two completely different stacks, but have them default to same network.
• I exec into service one_web-one and ping web-two. I will always connect to one_web-two.
• I exec into service one_web-two and ping web-one. I will sometimes connect to one_web-one but sometimes get two_web-one.

I would have expected that if I haven't referenced another stack, it would always default to the service inside of my stack?

Anyway, for now I can just give all services a unique name. Just wanted to check if this is a bug or expected?

The images below use Alpine links. You can install dig by running apk update && apk install bind-tools

Stack One:

version: "3.7"

services:
  web-one:
    image: tutum/hello-world
  web-two:
    image: tutum/hello-world

networks:
  default:
    external: true
    name: someoverlaynetwork

Stack Two:

version: "3.7"

services:
  web-one:
    image: tutum/hello-world

networks:
  default:
    external: true
    name: someoverlaynetwork

When I dig web-one from the web-two service in stack one I see:

/ # dig web-one

; <<>> DiG 9.10.4-P8 <<>> web-one
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33978
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;web-one.           IN  A

;; ANSWER SECTION:
web-one.        600 IN  A   10.0.0.50
web-one.        600 IN  A   10.0.0.55

;; Query time: 0 msec
;; SERVER: 127.0.0.11#53(127.0.0.11)
;; WHEN: Sun Jun 23 13:02:07 UTC 2019
;; MSG SIZE  rcvd: 71

10.0.0.50 is actually two_web-one 10.0.0.55 is actually one_web-one (or what I would expect web-one to resolve to)

Am I missing something?

[markwylde]

Closing, as this doesn't belong in this repo.