-
Psi correctly uses the SRV record to find the server to connect to, but when told to use a proxy, it simply asks the proxy to connect to domain portion of the JID. Given that the proxy doesn't know to…
-
It would be really useful to have all available endpoints with a single given Round Robin DNS entry as possible broker candidates. This simplifies a lot on the client side while allowing the broker s…
-
Session establishment failed on calling connect() method, because domain name and hostname is different...
any fix?
-
I have a strange issue. When I connect with sipML5 from a web browers to the oversip websocket server via www on port 10443 all is fine if the SIP server I am contacting is not on the same server as o…
-
Receiving that err for mongo atlas connection with stackstorm in kubernetes:
2021-12-27 12:39:16,014 INFO [-] Patching sys.stdout and re-opening it with utf-8 encoding (originally opened with UTF-8 e…
-
# Issue
It doesn't appear that DNS-SD is entirely supported due to the fact that DNS label names in DnsClient.NET strictly follow the recommendation in RFC 1035.
# Background
DNS Service Discover…
-
**What would you like to be added**:
Allowing multiple A records to be set from different sources that are managed by different external-dns instances.
For some background, I'm trying to create A …
-
We have a use case that we're trying to accommodate with prepared queries, but can't quite get to work. We're trying to setup puppet SRV records, https://docs.puppet.com/guides/scaling_multiple_master…
-
### Summary
When having a playbook with TLSA records in it, you can run in the first time where it creates the record, but the send time you run the exact same playbook Cloudflare returns: "API bad r…
-
Would be great to have support for Service Discovery (DNS SRV records) such as used by consul, Eureka, etc.
> replicas (type: array[string], allowed: TCP or HTTP URLs, default: empty) — Node repli…