Skip to content
This repository has been archived by the owner on Oct 23, 2024. It is now read-only.

are SRV records correctly implemented? #552

Open
f1-outsourcing opened this issue Jul 28, 2020 · 0 comments
Open

are SRV records correctly implemented? #552

f1-outsourcing opened this issue Jul 28, 2020 · 0 comments

Comments

@f1-outsourcing
Copy link

I have the impression that SRV records are not correctly implemented should ._tcp not be at the front (after the service) instead of in the middle? Or do I have something incorrect in my mesos configuration that makes these groups act as part of the task name?

[@]$ dig +short _sip._udp.sip.voice.google.com SRV
20 1 5060 sip-anycast-2.voice.google.com.
10 1 5060 sip-anycast-1.voice.google.com.

[@~]$ dig +short @192.168.10.14 server.temp.test.marathon.mesos
192.168.10.151

[@~]$ dig +short @192.168.10.14 _server.temp.test._tcp.marathon.mesos SRV
0 1 31682 server.temp.test-grxx9-s0.marathon.mesos.

(no output)
bash-5.0# dig +short @192.168.10.14 _tcp.server.temp.test.marathon.mesos
bash-5.0# dig +short @192.168.10.14 server._tcp.temp.test.marathon.mesos
bash-5.0# dig +short @192.168.10.14 _server._tcp.temp.test.marathon.mesos

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

No branches or pull requests

1 participant