Swarm dns fail after node restart

[gorazio]

Description
I have cluster with 3 manager nodes. And if restart one of node swarm stop to resolve some services via dns

Steps to reproduce the issue:

1. Deploy some services
2. Restart docker on one of the node
3. docker run --net swarmnet --rm -it alpine sh -c 'nslookup service'

Describe the results you received:
nslookup: can't resolve 'ms-frontend-v1.discovery': Name does not resolve
it has discovery at the end because i start it with network alias
Describe the results you expected:

Additional information you deem important (e.g. issue happens only occasionally):

Output of docker version:

Client:
 Version:      17.06.0-ce
 API version:  1.30
 Go version:   go1.8.3
 Git commit:   02c1d87
 Built:        Fri Jun 23 21:23:31 2017
 OS/Arch:      linux/amd64

Server:
 Version:      17.06.0-ce
 API version:  1.30 (minimum version 1.12)
 Go version:   go1.8.3
 Git commit:   02c1d87
 Built:        Fri Jun 23 21:19:04 2017
 OS/Arch:      linux/amd64
 Experimental: true

Output of docker info:

Containers: 1257
 Running: 102
 Paused: 0
 Stopped: 1155
Images: 316
Server Version: 17.06.0-ce
Storage Driver: overlay2
 Backing Filesystem: extfs
 Supports d_type: true
 Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins: 
 Volume: local
 Network: bridge host ipvlan macvlan null overlay
 Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: active
 NodeID: zqu4o84qkcus7cbcvp788sxya
 Is Manager: true
 ClusterID: g9khux33kxn2kcf6fkdyxfqfm
 Managers: 3
 Nodes: 3
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
  Force Rotate: 0
 Root Rotation In Progress: false
 Node Address: 123
 Manager Addresses:
  123:2377
  456:2377
  789:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: cfb82a876ecc11b5ca0977d1733adbe58599088a
runc version: 2d41c047c83e09a6d61d464906feb2a2f3c52aa4
init version: 949e6fa
Security Options:
 apparmor
 seccomp
  Profile: default
Kernel Version: 4.4.70-std-1
Operating System: Ubuntu 16.04.2 LTS
OSType: linux
Architecture: x86_64
CPUs: 8
Total Memory: 31.34GiB
Name: test-node-02
ID: G7M4:NFBE:P65E:MXP2:LL4P:66MM:ZUX7:F2V2:2S4R:3GXR:DTDQ:WMXS
Docker Root Dir: /srv/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
 lsyncd=true
Experimental: true
Insecure Registries:
 127.0.0.0/8
Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.):
Scaleway baremetal server

> docker service inspect  ms-frontend-develop
...
               "Networks": [
                    {
                        "Target": "sregfefq08fkrdi015548ew3w",
                        "Aliases": [
                            "ms-frontend-v1.discovery"
                        ]
                    }
                ],
...

> docker run --net develop -it --rm alpine sh -c 'nslookup ms-frontend-v1.discovery'
nslookup: can't resolve '(null)': Name does not resolve

nslookup: can't resolve 'ms-frontend-v1.discovery': Name does not resolve

[mimousewu]

Still, do not resolve. this issue last in many years.
Please give the result by
iptables -t nat -L -nv
Sorry, I cannot give the resolution. I just met this problem at 1.12.6 in CentOS 7.3 and last year at 1.11 in Ubuntu.
Here are some old issues related to this:
#23855
#13381
moby/libnetwork#947
#20026
docker/compose#5106
#34541
None of each can confirm resolved.

[thaJeztah]

Let me close this ticket for now, as it looks like it went stale.