[ https://issues.jboss.org/browse/JGRP-2316?page=com.atlassian.jira.plugin.... ] Bela Ban commented on JGRP-2316: -------------------------------- DNS_PING works perfectly on Google Container Engine (GKE) (see below); all members cluster correctly and dig also works consistently: {noformat} bash-4.4$ dig _ping._tcp.jgrp.default.svc.cluster.local. SRV ; <<>> DiG 9.12.3 <<>> _ping._tcp.jgrp.default.svc.cluster.local. SRV ;; global options: +cmd ;; Got answer: ;; WARNING: .local is reserved for Multicast DNS ;; You are currently testing what happens when an mDNS query is leaked to DNS ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 8968 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 3 ;; QUESTION SECTION: ;_ping._tcp.jgrp.default.svc.cluster.local. IN SRV ;; ANSWER SECTION: _ping._tcp.jgrp.default.svc.cluster.local. 30 IN SRV 10 33 7800 6136343230366238.jgrp.default.svc.cluster.local. _ping._tcp.jgrp.default.svc.cluster.local. 30 IN SRV 10 33 7800 6163393939366665.jgrp.default.svc.cluster.local. _ping._tcp.jgrp.default.svc.cluster.local. 30 IN SRV 10 33 7800 3236616662636137.jgrp.default.svc.cluster.local. ;; ADDITIONAL SECTION: 6136343230366238.jgrp.default.svc.cluster.local. 30 IN A 10.4.0.8 6163393939366665.jgrp.default.svc.cluster.local. 30 IN A 10.4.0.6 3236616662636137.jgrp.default.svc.cluster.local. 30 IN A 10.4.0.7 ;; Query time: 1 msec ;; SERVER: 10.7.240.10#53(10.7.240.10) ;; WHEN: Wed Dec 05 15:59:16 UTC 2018 ;; MSG SIZE rcvd: 218 {noformat} It would be interesting to see why (SRV) dig *never* returns an entry in the format {{172-17-0-5.jgrp.default.svc.cluster.local.}}, but always as {{6136343230366238.jgrp.default.svc.cluster.local.}} Also, all entries returned can be resolved by {{dig}} correctly, and there's never a single DNS resolution failure! I guess this leaves minikube as culprit and not alpine linux! -- This message was sent by Atlassian Jira (v7.12.1#712002)