srv-record

How to obtain Ip address of a kubernetes pod by querying DNS srv records?

ぃ、小莉子 提交于 2021-02-08 08:46:19
问题 I am trying to create a kubernetes job inside which I will run "dig srv" queries to find out the IP address of all the pods for any specific service running on the same cluster. Is this achievable ? I would like to elaborate a little more on the problem statement. There are a few services already running on the cluster. The requirement is to have a tool that can accept a service name and list down the IP addresses of all the pods belonging to that service. I was able to do this by using

Correct way to add a SRV record to Google Cloud DNS?

Deadly 提交于 2020-01-06 04:54:15
问题 I'm trying to add records needed to get my email working. When I try to add the SRV record to Google Cloud, the data text field template has only 3 numbers and a text ?? But on godaddy there are these fields that need to be add: Port, Protocol, Name, Service, Priority, Weight, Target. here is an example from godaddy: 443 _tls @ _sip 100 1 some-thing.some-thing Here is Google Cloud records form: So how should I add these data properly ? 回答1: it's a SRV record - which contains the SRV data:

Is there a way to make a websocket reachable through a SRV DNS record?

只愿长相守 提交于 2019-12-18 09:45:26
问题 I swear I googled this. I was wondering if there is any way to connect to a WebSocket service by resolving a SRV DNS query. In principle, this sounds reasonable to me, e.g., in a situation where the port where the service is going to be listening depends on the host and there is not a fixed port. For example: Server A listens with a WebSocket on port 1234. Server B listens with a WebSocket on port 1235. Server NS assigns a CNAME to A, and a CNAME to B. It also adds a SRV entry that points to

Is there a way to make a websocket reachable through a SRV DNS record?

╄→гoц情女王★ 提交于 2019-11-29 17:59:25
I swear I googled this. I was wondering if there is any way to connect to a WebSocket service by resolving a SRV DNS query. In principle, this sounds reasonable to me, e.g., in a situation where the port where the service is going to be listening depends on the host and there is not a fixed port. For example: Server A listens with a WebSocket on port 1234. Server B listens with a WebSocket on port 1235. Server NS assigns a CNAME to A, and a CNAME to B. It also adds a SRV entry that points to A's and B's CNAME s, and also points to each port. When connecting, an user should then connect to